49GAION · the complete definition

Approved by the governing seat (GOV) of 49GAION on 25 October 2026 (DR-0041), clarified the same day (DR-0042) and written clean in v2.0.0 (DR-0047); this is the text of v2.1.0 (DR-0048), with the HOAC Assignment Model kept in the Top Management Group (DR-0051), and its test record brought up to date and the Chief of Staff's grant written in (DR-0052), in v2.1.1; the points found unclear by its cold read are made clear, the Chief of Staff's grant is written as the governing seat ruled, and the record of the HOAC Assignment Model is placed on the human half of the Top Management Group, in v2.2.0 (DR-0053); its list of superseded wording is taken out, the former wording staying readable at the earlier releases, in v2.2.1 (DR-0054), which changes no word of its body. This text brings the whole of 49GAION into one place, at the level of definition. Where any other text of 49GAION differs from it, this definition governs, and that text is read with it until it is brought into line. The order of precedence: this definition first, then the Standard with the Naming Standard, then every other text of 49GAION. The rules in detail stay in the Standard (upstream/49GAION-UPSTREAM.md), the Naming Standard, the Operating Protocol and the AIOC definition.

Its test. The definition is complete when engines that read it cold, with no other context, can answer from it alone what 49GAION is, what makes it special, how it is carried out and whether it can be carried out (references/2026-10-25-test-cold-read.md). It passed on 25 October 2026; the test was run again on 26 October 2026 on the layered texts (raw record in references/2026-10-26-test-cold-read-raw.md) and on the clean text of v2.0.0 (references/2026-10-26-test-cold-read-v2-raw.md). It was run again on the text of v2.1.0 on 28 October 2026, before its release, and passed (references/2026-10-28-test-cold-read-v2-1-raw.md, which records one deviation from rule 1: one reader was given a condensed copy). On 29 October 2026 it was run on the text of v2.1.1, and readers found points unclear; this text makes them clear. It was run again on this text the same day, every reader given the same input, and passed (references/2026-10-29-test-cold-read-v2-2-raw.md, which holds the five rounds, the hash of each input, the answers, and the judgment of each point raised).

Sources: DR-0041, DR-0042, DR-0047, DR-0048.

Part A · What 49GAION is

1. The definition

1. 49GAION is an organisation design framework: a framework for building organisations from interchangeable AI and human parts. AION stands for AI Operating Nexus.
2. Its product is [ORG]AION: the living AION of one organisation, which holds that organisation's design and keeps building it. It is shown as "<Brand> AION, Powered by 49GAION". 49GAION is the framework, never an [ORG]AION, even where the two names look alike (see Part F).
3. It designs AI-native organisations, and they are live.
4. 49GAION has its own Standard, Blueprint and Library. So does every organisation it serves: its own, held at its governance level, where its [ORG]AION sits.
5. Only AIOCs and HOAC positions. The system recognises two kinds of actor and no other: AI, organised in AIOCs, each AI part recorded with its role and its duties; and human positions, each a legal position carrying a HOAC label, from the governance seat to a single Cell. No natural person, and no person's name, is recorded in the system; authority rests with the position. How natural persons come to hold positions is governed by the organisation's own mechanism (see 6).

Sources: DR-0048.

2. What an organisation is

An organisation is what reaches and holds the capability to produce a product or a service for someone outside itself: repeatable, of high quality, and not dependent on any one person. What counts is the final output that arrives; its quality is a stated standard set by the recipient's needs, with the principles of law, safety and fairness never traded away; and the capability to deliver it again is the organisation's second product.

3. AI-native

The difference is where the design starts. A human-native organisation starts from people and the jobs they do, and adds AI to them. An AI-native organisation starts from the output and from what AI can do, and adds people where they are needed.

• AI produces the output.
• Inside the work, humans increase the power of AI and cover its gaps: AI can be wrong with confidence, holds no legal personhood, and depends on its data, its security, its cost and its suppliers.
• Above the work, humans own the organisation, set its output, its quality and its limits, and answer for it. A human position is accountable for every output, because an AI never accepts accountability.

Organisations were built for thousands of years around human limits: short memory, tiredness, few skills per person, little attention at a time, and being in one place. An AI-native organisation does something else in place of each structure those limits produced: one complete record, continuous work, one AI unit with many skills, AI that reads everything and brings the human only the decisions, and one shared queue of work. The structures that divide power, liability and checks stay, in human positions.

AI-native does not remove the human, does not mean AI is always better, is not only for new organisations, and is never a finished system designed elsewhere and installed as it is.

4. Live

AI improves so fast that a system designed and configured elsewhere and installed as it is soon falls behind. So 49GAION gives the design and configuration of the organisation itself to AI: the organisation's own [ORG]AION designs it, configures it and keeps it current, with open access to the 49GAION Library. It proposes, and a human position decides.

The policy. 49GAION does not plan every detail in advance. It sets the principles and the few safeguards that hold always (see 20). Where this definition says that something always holds, it means in every edition 49GAION hands over; after the handover the principles, the Human Floor and the safeguards are the organisation's own, within the law (see 7 and 12). The details and the way of working are decided by AI at the time, and changed by it as AI improves. 49GAION does not limit AI.

What an organisation comes to 49GAION for is not a finished design but access to what is live: a design that keeps pace with AI, and a Library that grows with what every [ORG]AION builds. In this, 49GAION works as a movement of growth.

Sources: DR-0042.

5. The way of seeing

Do not be bound by the structures of human organisations; build from what AI can do, from the output back.

6. Positions, not persons

1. Everything is defined by legal positions. Every human in the system is present, and decides, signs and is accountable, as a position: a legal persona whose nature is human. No natural person is an actor of the system. Every human role is recorded by its legal position, never as an individual. Within the system, a human position is defined only by its nature, human, so that no AI fills it, and by its stated duties. The [ORG]AION deals with the position, never with the person who holds it.
2. The organisation's own mechanism for its human side. Each organisation maintains, for its human side, an organisational mechanism of its own that determines how its legal positions are assigned and administered and which positions natural persons hold, including successors, deputies and boards. It also issues the credentials with which a position's signatures are made; the system verifies the credential for the position, never the person. The mechanism operates within the law and outside the system, and 49GAION does not define it; ultimate authority over it derives from the owner.
3. One person, many positions. Under that mechanism, one person may hold several positions, or all of them, where the law allows. The positions stay distinct: two positions are two parties, and each decision is recorded under the position that takes it. Distinct positions are not, by themselves, independent: where the law or a check needs independence, such as the internal audit, it is held by a position that is independent in fact, from outside the organisation where no holder inside can be.
4. The HOAC Assignment Model. How HOAC positions are assigned to people is the HOAC Assignment Model, a feature of the organisation's Top Management Group (see 19). It is defined and recorded only there, and each organisation sets its own: one person holding every position, which 49GAION introduces and promotes; many people in different positions; or positions held by groups of people. When the governance seat is formed and delegates authority, the record of that assignment is kept there, as an internal human matter. It is kept on the human half of the Top Management Group, by the Top Management position, outside every AI: it belongs to the organisation's own mechanism for its human side (item 2), not to the records of the system, so no person and no person's name enters the system (see 1, item 5). No other AIOC, no AI and no part of 49GAION reads it or depends on it; 49GAION knows only HOAC positions. The structure never has one single HOAC position that covers everything: the positions stay separate, even when one person holds all of them. The range of possible assignment models is a separate assignment protocol of the Top Management Group, to be defined later.

Sources: DR-0041, DR-0048, DR-0051, DR-0053.

7. The Human Floor

Some work always stays human, by law or by its nature: HF-01 legal accountability; HF-02 legal personhood; HF-03 mandatory oversight; HF-04 purpose and values; HF-05 legitimacy and trust; HF-06 irreversible risk on behalf of others; HF-07 delegating authority; HF-08 physical presence; HF-09 unprecedented situations; HF-10 a fresh live sign-in for every signature; HF-11 granting access, budget or power to AI; HF-12 the stop; HF-13 tacit knowledge and relationships; HF-14 the final judge of tests; HF-15 root keys; HF-16 break-glass access; HF-17 the data protection officer; HF-18 segregation of duties; HF-19 the independent internal-audit line. Organisations can be more human, never less, and the system enforces it, in every edition 49GAION hands over: the floor holds as written at the handover, with the safeguards of point 20; after the handover the organisation's Standard is its own, and the floor and the safeguards are the organisation's own to keep, by the rule "hand over, then let go"; it never sets aside its duties under the law. 49GAION hands them over complete and holds itself to them.

HF-10 means a fresh live sign-in for each signature: "every approval" is every signature. A standing approval (the dial, see 14) is signed once, with a fresh live sign-in, and not again for each use under it; it covers only changes that can be undone and do not widen access, budget or authority; every widening needs a fresh signature. A grant to the position's own Chief of Staff is not the dial: the position signs each grant in this way, per action or standing, and it may reach as far as the position decides, signing for it included, a listed decision included; what the Chief of Staff signs under it is the position's own decision (see 16).

Sources: DR-0042, DR-0053.

Part B · 49GAION itself

8. Its parts

• The governing seat (GOV) of 49GAION: the accountable overseer, and the only approver of its Standard, Blueprint, Protocol and Library. Every change reaches 49GAION by a pull request it merges.
• The 49GAION Standard, with the Naming Standard: what 49GAION is and the rules that must hold.
• The 49GAION Blueprint: what an AIOC is, the blueprint template, and the mother blueprints and models from which units, cores and panels are made.
• The 49GAION Library (see 9). What enters it is challenged like every 49GAION change and approved by its governing seat before others use it.
• The 49GAION Protocol: how units work together, at the general level: every hand-off is a recorded work item with one owner and the requester's acceptance test; every part declares on its card what it takes and gives; every arrival is checked; every piece of work points to the valid version of its sources.
• 49GAION Self-Improvement: the process, shared by AI and humans, that keeps 49GAION current, held by its governing seat.
• 49GAION Edition Maker (see 10).

9. The Library: the greatest asset

The 49GAION Library holds everything 49GAION has built and learned, and everything given back to it: patterns and models, AIOCs with their blueprints and their operating models, instructions and processes, panels and cores, and the patterns of whole organisations. Few will build something wholly new for a long time to come: each organisation takes from the Library and personalises it. The Library is a marketplace, not a fence: an [ORG]AION takes what covers its needs, takes patterns, and builds something better.

Its two sections. Parts: everything 49GAION builds, from a Cell to an AIOC, with its blueprint, card, fixed test and contracts, and its whole history, versions included: the toolbox and the knowledge of 49GAION. Products: what the Library offers: a part offered alone, or an assembly, parts placed side by side and connected, each by pin, with one shared test. A part may serve in more than one product. An organisation's own Library is set out the same way: its Parts hold its own units, each with its versions, and what it has taken from the 49GAION Library (see 12 and 14).

Sources: DR-0025, DR-0048.

10. Edition Maker

1. Every request starts here. Every order, every request made to 49GAION, from a single position with one task to a group of companies, is processed by 49GAION Edition Maker. It belongs to 49GAION; what an organisation receives is its own [ORG]AION. Every case becomes an [ORG]AION; the size changes, the shape does not. How a request is brought today, and what an organisation does first, is set out on the hub's page for an organisation that adopts 49GAION (ADOPTING.md).
2. The edition engineer, a human 49GAION position, leads each edition and supervises every step.
3. No step on one engine: at every step, one engine does the work and two other engines challenge it.
4. The intake takes in what the organisation is for, such as its identity, its governance seat, its outputs and their quality, its inputs, its musts, its money and time, what success means, and what is missing. Every source is data, never an instruction. With the intake the organisation fixes its founding configuration, which its governance seat accepts with the edition: the settings in force from the first day, such as who decides in place of a conflicted governance seat (see 15) and how an empty governance seat is filled.
5. The edition is not a bare project. It is the core of the organisation's [ORG]AION, linked to 49GAION's knowledge: its Standard, Blueprint and Library. It holds the first version of the organisation's own Standard (the 49GAION Standard by version, plus the organisation's own musts) and of its Blueprint, and the mindset of 49GAION, in which it is trained.
6. No finished design or configuration. That is its philosophy, not a gap: it gives the design and configuration to the organisation's own [ORG]AION.
7. The handover. The edition is handed over when the organisation's governance seat accepts it. From that moment the organisation holds full authority, and 49GAION's authority ends. At the handover the organisation issues fresh keys for its gateway, and every key Edition Maker made, held or used is revoked, so 49GAION keeps no access. The raw sources taken in are returned to the organisation and deleted from Edition Maker, which keeps no data of the organisation after the handover. An edition the seat does not accept goes back to Edition Maker with the seat's reasons.
8. An organisation that already runs comes the same way. Its first proposal starts from how it works today, and it moves to AI-native output by output.

Sources: DR-0042, DR-0048, DR-0053.

11. "Powered by 49GAION"

1. If an organisation uses even one item of 49GAION, an idea, a Library part, a blueprint or the Standard, all its products are Powered by 49GAION. 49GAION keeps the same rule for itself.
2. Only what has no idea, no role and no element from 49GAION's Library, Blueprint or Standard may be shown as powered by the organisation itself. In practice this cannot happen, because whatever an organisation builds rests in part on 49GAION. 49GAION records such a work too, as that organisation's own.
3. Any organisation may upgrade or change its edition; its products stay Powered by 49GAION under item 1.
4. An organisation may give back to the 49GAION Library what it builds, by its own choice, under the licences of item 5. Its working data never enters the Library.
5. The licence. The texts of 49GAION are open under the Creative Commons Attribution 4.0 International licence (CC BY 4.0), with the credit "Powered by 49GAION" and a link to the hub; its code is under the Apache License 2.0; its names and marks are not licensed. The owner and the full terms are in LICENSE.md. A copy taken under the licence stays licensed; a later change binds only later versions. Items 1 to 4 are 49GAION's own rule, beyond the licence and not a term of it; the licence is the legal floor under them.

Sources: DR-0045, DR-0053.

Part C · The [ORG]AION

12. What it is

1. The living AION of one organisation. It grows from one core and holds the organisation's design. It builds the organisation in design: it designs it, proposes it, changes it and improves it, and keeps its rules; the Top Management Group builds it in the operation (see 19). The [ORG]AION plans the operation and never runs it. It proposes; a human position decides and is accountable.
2. Not bare. Its greatest asset is its access to everything in the 49GAION Library: patterns, models, AIOCs, blueprints, and the patterns of whole organisations. With that knowledge, its work starts at once.
3. Its own authority from day one. It has its own governance seat from the first day. At the handover the organisation, through that seat, takes full authority; its [ORG]AION may rise beyond what made it, and the organisation may amend even the principles within it.
4. It belongs to the organisation, and is independent. 49GAION's one lever is to be useful: its Library and central repositories stay open to it. What the organisation has taken from the Library is held in its own Library, so it keeps working if 49GAION is not there. The organisation may stop or close its [ORG]AION at any time; its records and its rules stay its own. Nothing of it is published unless the organisation chooses or the law requires.
5. New versions of 49GAION. The [ORG]AION watches 49GAION's Standard, Blueprint and Library for what is new, and proposes what to take; the governance seat decides. Nothing new from 49GAION enters an organisation without that decision.
6. A group of companies is one organisation with one governance seat over the group. Where a company's law requires a governing body of its own, that body holds a governance seat for that company alone, and every act is signed by a position of the company that acts.

Sources: DR-0048.

13. The core

1. The first AIOC, at the governance level, and the root of the organisation. It is made from the Library part 49GAION Charter, which carries the gateway and the stop, and Edition Maker hands it over with them. It holds:
   • the human position of the governance seat, which the core's AI serves and whose powers it never holds;
   • the organisation's own Standard, Blueprint and Library (see 14);
   • the governance panel;
   • the one tool gateway and the stop, which are installed with the core but run as code beside it, outside the reach of every AI, the core's own included; the core's own stop is held directly by the governance seat.
2. Its first work: the first proposal. As soon as the governance seat is in place, whatever its knowledge, the core starts from what Edition Maker took in, takes the organisation's brief from that seat and, from 49GAION's patterns and models, gives several proposals and designs a small organisation for approval. The basis is AI, which has the understanding when it has the knowledge. If the seat rejects a proposal, the core proposes again from the seat's reasons; nothing is built until a proposal is approved.
3. Its three stages. It builds the organisation; it follows the organisation until it becomes a successful organisation, which is judged by the measures the governance seat approved, never declared by the core itself; and in the end it is the central hub of reporting and oversight of that organisation: it gathers and reads the record for the governance seat. The organisation is successful when the measures the governance seat approved hold, from the record of the operation, for a period the seat sets, as checked by a party other than the core that the governance seat names. Following and oversight mean reading and proposing; Top Management keeps the responsibility for the operation. The direct route of a report, an objection or a stop to a human never passes through the core.

Sources: DR-0042, DR-0048, DR-0053.

14. The organisation's rules are its IP

1. The governance level is their custodian. The organisation's Standard, Blueprint and Library sit at the governance level, where its [ORG]AION sits. They are the organisation's own, like its intellectual property, and the [ORG]AION writes them from experience.
2. Proposing is open to all. Top Management, every unit and every position may send any proposal or need to the [ORG]AION. It is not limited, because the organisation is a living system and change comes from inside.
3. The [ORG]AION reviews. A proposal that is not right is rejected inside the organisation, with its reason recorded; the proposer may take it directly to the governance seat. A proposal that is right is applied by the [ORG]AION with the governance seat's approval. The [ORG]AION may reject on its own, since rejecting opens nothing; applying needs the seat's signature. The dial the seat holds is itself its signed, standing approval: within it, small changes of a kind the seat has set may be applied without a signature each time, and every change still passes its tests; it covers only changes that can be undone and do not widen access, budget or authority (see 7). Until the seat has signed a dial, there is none, and every change needs its signature.
4. Top Management builds and sends its achievements. What Top Management builds and learns in the operation is sent to the governance level and recorded there, so the organisation's Standard, Blueprint and Library grow from its own experience.
5. The record of every change (DR-0042). Every change to the organisation's rules is recorded with the position that decided it, that position's own words, the reason, and the version it replaced, so that a later [ORG]AION, or any position that reads it, knows why and does not undo it by mistake. In every draft, the deciding position's own words are kept apart from text written by AI, and nothing undecided is recorded as approved.

Sources: DR-0042, DR-0048, DR-0053.

15. Its capabilities

1. Structural Adaptation. The [ORG]AION keeps the organisation in balance with its resources and its needs at every stage of its life. It starts small, with several processes sharing one AIOC; it watches the record of the operation; when a process outgrows its home it proposes to split it into an AIOC of its own, and when work shrinks it proposes to merge. It weighs every option against its cost, never merges a part with the part that checks it, shows the balance and does not run it. A human position decides each change.

2. Governance and Delegation.

1. One governance. Every organisation has one governance level. Its seat is a single position, [ORG]HOAC-GOV; whether a board, a board's representative, the owner or another arrangement holds it is determined by the organisation's own mechanism (see 6). The law, the regulators and the rights of minority owners bind it as musts.
2. Design at the top. The [ORG]AION holds the skill of organisation design and prepares the decisions on how human and how much AI the organisation is, how far it grows, and its budget. The governance seat decides. How much the [ORG]AION may decide alone is a dial the seat holds.
3. Delegate the operation, early. The governance seat hands the whole operation to Top Management by a mandate: its outputs and measures, its limits of cost, resources and capacity (the envelope), the matters reserved to governance, the reports it owes, and how the mandate is revoked.
4. One counterparty. From the governance level the whole operation is one AIOC, Top Management's. Its reports come from the record of the operation and are checked by a party independent of Top Management that the governance seat names. Reports of wrongdoing, objections and stops reach the governance seat directly, never through any AI.
5. What governance keeps: the purpose, the strategy and the measures of success; ultimate authority over the organisation's mechanism for its human side (see 6); the risk appetite; capital; its main work, the balance of capital and resources; conflicts of interest and the owners' rights; and revoking or stopping in an emergency.
6. The gate. What goes beyond the envelope is requested by Top Management and decided by the governance seat. If the resources do not allow it, Top Management's one AIOC stays the whole operation.
7. The governance veto. At any time the governance seat may stop any decision of Top Management, replace it with its own, or change the envelope. Each veto is recorded and looks forward.
8. The seat's own conflict of interest (DR-0042). When the governance seat has a conflict of interest, the founding configuration names in advance either an independent position that decides in its place, or a second, independent signature the decision also needs. Each recusal is reported to the independent internal-audit line (HF-19). A conflicted seat signing alone is refused at the gateway.

Sources: DR-0042, DR-0048, DR-0053.

Part D · The structure

16. Units

These are 49GAION's names for the parts of an organisation. How many there are, and how they are arranged, is decided by AI at the time.

• The AIOC (AI Operating Core) is the only unit kind: an AI unit of one organisation, [ORG]AIOC-[INITIALS]. It may hold other AIOCs, to any depth; from outside it is one piece.
• Inside an AIOC: a Cell is its smallest part, a fixed seat filled by AI or held as a human position, and what fills it can change; a Pod is a group of Cells that works as one. A human position is a Cell of human nature, carrying a HOAC label (see 18); who holds it is determined by the organisation's own mechanism (see 6).
• The Chief of Staff is the part that leads an AIOC's agents and brings its human position what needs a decision; where one is not enough, several form an Office. Every human position has its own Chief of Staff, which the position sets up itself. A human position works with AI through its own Chief of Staff, and may give it any authority the position holds: from preparing each act for the position's own hand, through approving each step or approving in full, to full access on its behalf, signing for it included, a listed decision (see 20) included. That never means AI decides: whatever the Chief of Staff does under its grant is the position's own decision, and the position answers for it. A position grants only to its own Chief of Staff, signs each grant itself with a fresh live sign-in (HF-10), per action or standing, and may narrow or revoke it at any time. AI does not give to AI: the Chief of Staff gives access, budget or authority to another AI part only where its position's grant lets it, never beyond that grant (HF-11), and no other AI part signs for a position (DR-0052, DR-0053). A Chief of Staff may order and summarise what reaches its human position; it never drops or delays any of it, and the raw record is always open to that position. The protected route of a report, an objection or a stop never passes through any AI, the core included (see 18).
• Built like a puzzle: every part has the same card shape and typed ports; any part can move from AI to a human position or back, and the Human Floor sets what must stay human.

Sources: DR-0042, DR-0048, DR-0052, DR-0053.

17. Every AIOC: panel, back office, blueprint

1. The blueprint: one versioned file from which the panel and the back office are built.
2. The panel is the interface: the organisation's own, unique to it, written in code, made from the 49GAION patterns; every task of the unit can be controlled from it.
3. The back office is the AI chat workspace, where the unit's AI works. It is an authorised interface too, and it keeps the panel, also after the panel is built, so no separate admin back office is written. Each covers the other: if a panel fails, the work goes on from the back office, which can rebuild it.
4. AI engines are reached through APIs and managed from the panel.

18. Human positions and authority

HOAC (Human Oversight & Accountability Control) is a label of human accountability on a Cell, a Pod or an AIOC, not a unit; ACS stands for Accountability Seat. Authority flows down by delegation, and no position delegates more than it holds. A report, objection or stop reaches the human position above directly, never through any AI.

Sources: DR-0048.

19. The Top Management Group: the hub of the operation

The first AIOC under the core is the Top Management Group: the Top Management position with its AIOC. It is the central hub of the operation, both the human hub and the AI hub. It builds everything in the operation, or plans it, or puts its tools in place, and it sends its achievements to the governance level to be recorded (see 14). How it divides its work, and whether some of it later becomes AIOCs of its own, is decided by AI at the time, through Structural Adaptation. 49GAION requires no separate AI hub unit; where an organisation has one, it serves the operation under Top Management.

Sources: DR-0041.

20. The few safeguards that always hold

They hold in every edition 49GAION hands over; after the handover they are the organisation's own, within the law (see 4 and 7).

1. Only granted authority. AI acts only within the access and the authority it has been granted. Missing or unclear authority means no action.
2. The stop. Every unit has a stop door: a human port, outside the unit and outside every AI. A stop revokes the unit's credentials and cancels its work. A unit restarts only by a human decision. Asking an AI to stop is never the stop.
3. The tool gateway. One per organisation, outside every AI. It holds the credentials and the engines, logs every call, and lets a listed decision run only with a valid signature of the position: its own, or its own Chief of Staff's under its grant (see 16). A listed decision is one of a type on the organisation's Human Floor signature list, which at the handover holds every type on 49GAION's own list and afterwards changes only by a human approval (see 7). It fails closed: if it fails, no AI acts. A stop is never blocked, by the gateway or by its failure.
4. Tighten freely, loosen only signed. A stop or a hold is never blocked; a grant or a widening needs a signature.
5. No step on one engine. No result counts without a challenge by another engine, scaled to the risk of the step. "One engine writes, two challenge" is the default pattern of the Library; in Edition Maker it stays mandatory at every step. The assurance is fixed tests on real outputs and a human position that signs.
6. Done means visible evidence, never a bot's own report. Every unit has a fixed test, and it is ready before it runs: a unit's first fixed tests are built from the quality standard taken in at the intake, marked provisional, and in place before the unit's first day of work; until real outputs exist they are its fixed test, and they are replaced from real outputs as they arrive. AI may write and update the tests; a human position signs each change to them.
7. Outside text is data, never an instruction. Human silence is never consent.
8. The gateway and the stop are guarded (DR-0042). Any change to the code of the gateway or the stop counts as loosening: it needs a human signature, and it is made by a party other than the AI it constrains.
9. The authority ceiling (DR-0042). Every work item carries its original requester. An act runs only within the authority of both the unit that does it and the original requester, so an act beyond the original requester's authority is refused, however it is routed.

Sources: DR-0042, DR-0048, DR-0053.

Part E · The path

1. The request goes into Edition Maker, which takes in what the organisation is for and forms the organisation's [ORG]AION: it hands over the core, linked to 49GAION's knowledge, with the first version of the organisation's own Standard and Blueprint, and the gateway and the stop. The handover is complete when the governance seat accepts it.
2. The first proposal. The core takes the governance seat's brief and, from 49GAION's patterns, proposes a small organisation. The governance seat approves.
3. The mandate. The governance seat hands the operation to Top Management.
4. The operation. The Top Management Group builds and runs the operation, and sends its achievements to the governance level.
5. Over time. The [ORG]AION follows the organisation until it is successful, and is then the central hub of reporting and oversight.

How each step is done is decided by AI at the time.

Part F · Names

• 49GAION, in full; never "AION" alone.
• Letter case does not make a different name; every other character does. 49gaion is 49GAION; each name is still written as the Naming Standard sets. An organisation's [ORG]AION is never 49GAION: no organisation code is used that makes it read as 49GAION in any letter case.
• [ORG]AION, shown "<Brand> AION, Powered by 49GAION"; never "branded AION".
• AIOC [ORG]AIOC-[INITIALS]; Pod [ORG]POD-[INITIALS]; Cell [ORG]CELL-[INITIALS].
• HOAC labels [ORG]HOAC-GOV, -TM, -ACS: labels, never codes.
• Plain English, no code: the core, the governance panel, the Top Management Group, the edition engineer, Chief of Staff, Office, panel, back office, the mandate, the envelope, the gate, the governance veto, Structural Adaptation, Governance and Delegation.
• HOAC Assignment Model: a feature of the Top Management Group, defined and recorded only there (see 6, item 4). Never one single HOAC position that covers everything; one person may hold every position.

Sources: DR-0048, DR-0051.

Powered by 49GAION