Purpose
Why the department exists inside the enterprise and which enterprise objectives it serves.
Departmental Anunnaki Twin
Give every department a computed operating field.
A Departmental Anunnaki Twin is the governed computational counterpart of one organisational unit inside the Enterprise Anunnaki Twin. It connects departmental objectives, professions, systems, authority, dependencies, Necessary Work, meetings, performance and continuity.
Form a Departmental Anunnaki TwinThe operating hierarchy
Enterprise Anunnaki Twin
The whole enterprise
Departmental Anunnaki Twins
Bounded organisational units
Professional Anunnaki Twins
Authorised professional capacity
Department is not profession
The Departmental Anunnaki Twin maps the organisation. The Professional Anunnaki Twin maps the profession.
Finance may contain accountants, auditors, tax professionals, analysts and administrators. Legal may contain lawyers, compliance professionals and contract specialists. One professional may contribute to several departments. Every connection therefore records a departmental responsibility and authority state instead of assuming authority from membership alone.
Required outcomes
The states the department must establish, maintain or change.
Professional composition
The professions and roles connected to the department without confusing department membership with professional authority.
Authority
What the department may observe, prepare, communicate, decide, approve, spend or execute.
Systems
The departmental software, records and information sources explicitly approved for use.
Work state
Departmental work that is Established, Latent, Silent, Refused, waiting, active or settled.
Necessary Work
The ordered work raised from the difference between the observed departmental state and the required state.
Dependencies
Work waiting for another department, an external professional, evidence, approval, time or verification.
Continuity
The departmental state that remains when a professional changes roles or leaves the enterprise.
Performance
The condition of the work system measured through outcomes, waiting conditions, settlement and continuity rather than unexplained employee scoring.
Departmental Necessary Work
Work is raised from a departmental state, not dropped into a generic task list.
Choose the Departmental Anunnaki Twin
Name the organisational unit whose state is being observed.
Record the observed state
Show what is presently established without treating an assumption as evidence.
State the required outcome
Define the departmental successor state and the profession required.
Establish authority
Name who may observe, prepare, communicate, decide or execute.
Define completion proof
State what must be verified before the work can settle.
Derive Necessary Work
God Code computes the unresolved difference and the affected dependencies.
Route professional capacity
The work moves to an authorised internal or external Professional Anunnaki Twin.
Write the successor state
Verified completion updates the Departmental Anunnaki Twin and the Enterprise Anunnaki Twin.
Meetings between departments
A meeting becomes an authorised Departmental Anunnaki Twin Workroom.
Departments do not gain unrestricted access to each other because they belong to the same enterprise. A Departmental Anunnaki Twin may know more than it is authorised to disclose. Every Workroom begins reserved until ABOS can establish the common authority required for the meeting.
Correct initial state
RESERVED PENDING AUTHORITY REVIEW
The current corporate onboarding creates the Workroom record and correctly refuses to represent the meeting as open before its authority is admitted.
Before the meeting can open
- A named enterprise objective
- The participating Departmental Anunnaki Twins
- The Professional Anunnaki Twins authorised to represent each department
- Permitted topics
- Sender disclosure authority
- Recipient receiving and use authority
- Departmental decision authority
- Human reserved decisions
- Escalation to the Enterprise Anunnaki Twin
- Time, validity and jurisdiction
- The evidence required for settlement
Remove the friction between ManCo and ExCo
ManCo gives ExCo a complete decision. ExCo gives ManCo an authorised direction.
ManCo should not spend days rebuilding operational context for every executive meeting. ExCo should not have to search through departmental noise to discover what it must decide. The Enterprise Anunnaki Twin turns an unresolved departmental condition into one governed executive decision packet. ExCo decides, reserves or requests more evidence. God Code then identifies the affected field and returns the decision to ManCo as ordered Necessary Work.
Decision required
The exact reserved decision ExCo must make, separated from operational detail that does not affect it.
Business context
The enterprise objective, affected Departmental Anunnaki Twins and current operating state.
Established evidence
The facts, records, provenance and verification on which ManCo relies.
Options
The lawful choices available, including the option to reserve or seek more evidence.
ManCo recommendation
The operating recommendation from the people responsible for delivery.
Consequences
The effects of each option and of delaying the decision across cost, work, time, authority and dependency.
Executive authority
The role, policy, delegation or board authority required to make the decision.
Decision deadline
The latest lawful or useful time for the decision, including expiry consequences.
Departmental signal
A Departmental Anunnaki Twin identifies a condition that cannot settle within ManCo authority.
ManCo packet
ManCo records the decision, evidence, options, recommendation, consequences, authority and deadline.
Corporate consolidation
The Enterprise Anunnaki Twin joins effects across departments without exposing unrelated information.
ExCo decision
ExCo uses its reserved authority to decide, reserve or request more evidence.
Decision receipt
ABOS records who decided, the authority used, what was known and when it happened.
Affected field
God Code identifies the connected obligations, dependencies, deadlines and work states changed by the decision.
Return to ManCo
The decision becomes an authorised successor instruction and ordered Necessary Work for the responsible departments.
Verification
The enterprise records completion only when the required evidence proves the successor state.
READY FOR EXCO REVIEW
ManCo has completed the bounded packet and the reserved decision is waiting for ExCo.
DECIDED AWAITING SUCCESSOR VERIFICATION
ExCo has decided and ManCo has the instruction, but completion is not yet proved.
SETTLED
Required evidence verifies the successor state and closes the decision loop.
The BRC example
A signature should not automatically cost every department one hour.
When a bid exceeds the Business Risk Committee threshold, the Enterprise Anunnaki Twin creates one versioned decision package. Legal comments already submitted remain attached. Every required department records its decision against the same package digest. ABOS shows who has signed, which authority they used, what is still missing and whether the deadline is approaching.
If every required department approves the same version, the committee chair can close the decision without convening the routine meeting.
A meeting is raised only for an exception
- A department disagrees or declines
- Approval contains a condition
- Evidence or the bid package changes
- Required authority is missing or expired
- A conflict or recusal must be resolved
- A material risk remains unresolved
- The signoff deadline expires
Open circulation
A bid above threshold becomes a named committee matter with a deadline.
Freeze the package
The evidence, prior comments and decision question receive one package digest.
Collect decisions
Each Departmental Anunnaki Twin approves, conditions, reserves, requests change or declines under recorded authority.
Watch completeness
The Enterprise Anunnaki Twin shows every required signoff and prevents a signature from moving to a different package version.
Raise exceptions
Any non approval state raises a meeting exception instead of pretending consensus.
Close without meeting
Unanimous approval allows the authorised chair to close the decision asynchronously.
Issue receipt
ABOS records the package digest, departments, decisions, authority, time and closeout.
Verify execution
Approval becomes Necessary Work and remains open until the bid action is proved.
What Linda in Legal receives
Her legal comments are submitted once, attached to the correct package version and remain visible to authorised departments. She can see whether every department has responded without attending a meeting whose only remaining purpose is to collect signatures. If the package changes, her prior signature cannot silently carry forward to the changed matter.
Departmental performance
Measure the movement and condition of work before judging people.
The Departmental Anunnaki Twin reports whether outcomes are being established, why work is waiting, whether capacity exists and whether the department could continue through change. It does not convert activity into an unexplained employee score.
Outcome state
Which required departmental outcomes are established and which remain unresolved.
Work movement
Necessary Work raised, active, waiting, admitted, settled or refused.
Authority pressure
Work delayed because decision or execution authority is absent.
Evidence pressure
Work delayed because required evidence, provenance or verification is absent.
Dependency pressure
Work waiting for another department, person, system or external Professional Anunnaki Twin.
Time pressure
Approaching deadlines, validity limits and expiry events.
Capacity
Available Professional Anunnaki Twin capacity compared with the work required by the department.
Continuity readiness
Whether another authorised professional could continue the departmental work without reconstructing it from fragments.
Subscription allocation by department
One corporate subscription. Capacity and performance visible by department.
The enterprise receives one consolidated account while the Enterprise Anunnaki Twin shows how Departmental Anunnaki Twins, Professional Anunnaki Twin connections, system connections, external work and verification capacity are allocated. Interaction between authorised Anunnaki Twins and the ManCo to ExCo decision bridge are included operating capacities, not a separate charge for every collaboration or decision.
Subscription componentWhat the enterprise receives
Enterprise Anunnaki Twin CoreThe enterprise identity, corporate authority, consolidated work state, continuity and corporate reporting.
Departmental Anunnaki Twin allocationOne bounded departmental computation containing purpose, objectives, systems, authority, Professional Anunnaki Twin connections and work state.
Professional Anunnaki Twin connectionsThe staff Professional Anunnaki Twins connected to each department under declared and later verified authority.
System connectionsApproved enterprise or departmental software connections and their action boundaries.
External professional workBounded work raised to qualified Professional Anunnaki Twins outside the enterprise.
Verification capacityIndependent verification, receipts, successor state admission and settlement.
Current corporate formation practice
The enterprise workspace now lets the corporate owner form Departmental Anunnaki Twins, connect professionals to departments, allocate subscription capacity, raise Necessary Work from a selected department, monitor departmental work states, declare cross departmental Workrooms and operate the ManCo to ExCo decision bridge. Executive decisions return to ManCo as successor instructions that remain awaiting verification until completion evidence is established.
Theory becomes operating structure