Ivory & Co.
AEA by Ivory & Co.StandardsKnowledge & ResearchImplementationCertificationIvory & Co.
Ivory & Co./Standards/Publication 14 · Governance 01 of 02

AEA by Ivory & Co. Governance Standards

The architecture of governed consequence.

Govern the consequence, not the creativity.

Every enterprise changes.

People develop ideas, challenge assumptions, investigate possibilities and experiment with different ways of working. Some ideas remain conversations. Others become prototypes, proposals, operating practices or decisions that materially alter how the enterprise runs.

Businesses rarely lack change. What they struggle with is telling the freedom to explore something from the authority to make it consequential. An idea may be harmless while it is an experiment. The same idea creates real obligations once it becomes an approved operating instruction, a customer commitment, a financial decision or a dependency other parts of the enterprise rely on.

AEA’s Governance System deliberately separates innovation from embedment, so exploration can happen without the requirements that attach to governed change. When an activity creates, changes, removes or materially threatens a protected condition, governance has to recognise and address that consequence. The AEA Governance Standards establish the normative protections, conditions and required behaviours through which the distinction is maintained.

The freedom to explore

Organisations introduce governance because they want more control over change, and the intention is sound. Poorly designed governance creates a different problem. Every idea becomes a proposal. Every experiment needs approval. Every variation is treated as a threat. The organisation gets better at controlling change and worse at discovering what should change.

Under AEA Governance, creativity, novelty, contradiction and experimentation are not subject to change governance simply because they exist. An enterprise can explore several business models without committing to any. A team can investigate an alternative method without replacing its established instructions. A researcher can challenge an architectural proposition without acquiring the authority to change it.

Exploratory work is still bound by legal, privacy, security, contractual and intellectual property obligations. The point is that change governance is engaged by the consequence involved, whatever the novelty of the thinking.

When an idea becomes consequential

A business experiments with an intelligent agent, testing whether it can interpret customer enquiries, retrieve information and recommend responses. The experiment produces useful findings and alters nothing in the approved operating arrangements.

Then the agent begins answering actual customers as part of the service operation. Now it influences customer experience, operational commitments, information use and the conditions under which the enterprise relies on automated activity.

That transition can happen without anyone submitting a change request. A prototype is connected to a production system. An informal practice becomes widely adopted. An experimental document starts being treated as authoritative. AEA Governance recognises both intended and unintended embedment. It is engaged when governed consequence is deliberately sought, actually arises or is reasonably suspected to have arisen, so the absence of paperwork is never mistaken for the absence of consequence.

Governance begins with what is being governed

A document is not necessarily a standard. A record is not the object it describes. A report can present authoritative information without being the source of that authority. A stored experiment is not a governed architectural proposition.

An enterprise keeps a register of its capabilities. The register is a useful representation, and it is not the underlying architecture. If the same information appears in a dashboard or another application, the enterprise must not end up with competing truths. The Governance Standards distinguish governed objects, records, representations and compositions, and set requirements for persistent identity, provenance and relationships.

Authority must be explicit

A person can have access to a system without authority to change what it holds. A manager can approve a commercial decision without authority to redefine the rules governing it. An intelligent agent can be technically capable of an action without authority to decide whether it should occur.

Authority must be explicit enough to establish what is permitted, within which scope, under which conditions and for how long. Delegated authority must stay bounded, traceable and revocable. The technical capabilities of a system must never silently expand the authority under which it operates.

Knowledge must keep its identity and history

Standards are revised. Decisions are superseded. Instructions are amended. Propositions are divided, combined or replaced as understanding develops.

A business renames an operating capability. The name changes and the capability is the same object. A material change in meaning, by contrast, may need a new identity or an explicit supersession. Governed identity stays distinguishable from location, representation and version: a document moved between repositories keeps its identity, and a historical reference stays meaningful after the current publication changes. People and machines can then tell what was authoritative, what is authoritative now and how the enterprise got here.

Governance should be inherited

As organisations grow, governance fragments. Departments write their own policies, projects add approval mechanisms, technology teams build controls, and operating units keep separate interpretations of rules that should apply everywhere.

The Governance Standards establish that a rule is defined at the highest level at which it is universally valid. Specialised governance inherits it and adds what its context needs, preserving the intent and constraints of the parent unless variation is expressly permitted. Conflicts are determined by the appropriate authority, never by document order, repository location or convenience.

Governance must remain proportional

A minor change to an internal presentation does not need the treatment of a change to a critical operating instruction. Governance scales with consequence, and size is a poor guide: a small adjustment can affect a material obligation, and a large experiment can carry little governed consequence while it stays contained.

Consequence can also change while the object stays the same. An existing document acquires new significance because it starts being used for a different purpose. A previously acceptable arrangement needs reassessment because its scale, audience or reliance conditions have changed. Governance therefore concerns continuing applicability as well as the approval of discrete changes.

No straight line required

An investigation reveals another question. A solution needs several iterations. Teams explore related possibilities at once. The Governance Standards assume no universal lifecycle. They permit recursive, concurrent and interacting loops while preserving ownership and consequence boundaries. What matters is whether an activity remains within its current governed conditions or crosses into a context carrying different consequences.

Governance for humans and machines

A rule buried in an inaccessible document is hard to apply. A requirement without a stable identity is hard to reference. An approval whose authority cannot be established is hard to verify. The Governance Standards require governed knowledge to be addressable, discoverable, traversable and retrievable with enough context for correct use. Sophisticated governance should support simple execution, so that nobody has to become an expert in governance doctrine to act correctly.

The thirteen Governance Standards

The Governance Standards are organised through thirteen parent concerns, GOV-01 to GOV-13. Together they establish the protections needed to govern the Governance System itself, the identity and treatment of governed objects, authority, provenance and the other conditions for governed knowledge and action. They derive their protections from the companion Governance System Design, which holds the architectural reasoning.

An adaptive enterprise needs freedom to explore alternatives, and confidence that the move from exploration into consequential operation is deliberate, recognisable and governed. Govern the consequence, not the creativity.

Publication record

Publication
AEA Governance Standards
Version
v1.0.1
Status
Published baseline — editorial correction. Clarifies present-state operating language without changing the approved Governance doctrine.
Scope
Thirteen parent Governance Standards, GOV-01 to GOV-13
Steward
Ivory & Co.
Integrity
SHA-256 856e85e88a7b0c8c9f1e58e248fa15f6a531cd2418d5ec7c25f71308bf3b72ac
Related
Governance System Design · AEA Design · Architecture Set Standard
Download PDF© 2026 Ivory & Co. · Licence terms to be confirmed
·Full publication

Governance Standards v1.0.1

The complete text, in its original section structure and governed wording.

Adaptive Enterprise Architecture --- Governance System

v1.0.1 — Published Baseline — Editorial Correction

Status: Published — v1.0.1. This editorial correction clarifies present-state operating language without changing approved Governance doctrine.

This published baseline preserves the thirteen-parent Governance architecture while explicitly separating the AEA Governance System Design from the normative Governance Standards derived from that Design. Architectural observations produced by applying the eleven AEA Standards to Governance are held in the companion Governance System Design. This document contains the governing protections, conditions and required behaviours derived from that Design.

System anchor: There is a deliberate separation between innovation and embedment.

Governing principle: Govern the consequence, not the creativity.

Operational corollary: Governance is engaged when governed consequence is intentionally sought, actually arises, or is reasonably suspected to have arisen.

The Governance System does not prescribe the upstream innovation environment. It governs the transition into structured alignment and governed consequence, including consequence that emerges without deliberate submission. Governed progression is non-linear; lifecycles may differ by context; loops may be nested and interacting; and consequence may change without the underlying object changing.

This set deliberately does not invent final canonical identifier grammar, universal lifecycle labels, final disposition vocabulary, certification model, technical schema, repository technology, assurance scoring, or detailed contractual/IP terms. Where those remain unresolved, semantic requirements are stated without manufacturing implementation vocabulary.

Temporary GOV-xx-Pxx references are development references, not final canonical AEA proposition identifiers.


GOV-01 --- AEA Governance System Standard

Purpose and boundary

GOV-01 governs the Governance System as a system. It establishes the rules by which governance concerns are bounded, related, inherited, specialised and applied. It does not absorb the detailed subject matter owned by GOV-02 through GOV-13.

Its purpose is to keep governance coherent while allowing specialised governance to exist where different governed objects genuinely require different treatment.

Governing propositions

GOV-01-P01 --- Governance rules are established at the highest level at which they are universally valid and inherited by applicable subordinate governed contexts.

GOV-01-P02 --- Specialisation may add specificity but must preserve parent intent and constraints unless variation is expressly permitted.

GOV-01-P03 --- Inheritance follows applicability and lineage rather than a mandatory fixed-depth hierarchy.

GOV-01-P04 --- A change to a governing proposition requires assessment of inherited blast radius across applicable specialisations and active instances.

GOV-01-P04A --- Where multiple applicable specialisations produce incompatible requirements, the conflict must be explicitly determined through the authority applicable to that consequence. The determination must preserve the inherited protection intent, identify the propositions and contexts in conflict, record the basis and authority for resolution, and must not silently establish a new parent rule.

GOV-01-P05 --- Governance has authority over the governance process; it does not invent architectural truth.

GOV-01-P06 --- Governed knowledge must be addressable, discoverable, traversable and retrievable for human and machine consumers with sufficient authority, currency, applicability and lineage context to establish correctness for intended use.

GOV-01-P06A --- A normative Governance proposition must retain traceable relationship to the Governance System Design requirement or requirements it gives effect to. That relationship preserves design rationale and lineage; it does not transfer semantic ownership between the AEA Architecture Set, Governance System Design and Governance Standards.

GOV-01-P06B --- Where a protection protocol composes propositions from more than one Governance Standard, the protocol does not become the semantic owner of those propositions. Each constituent proposition retains its governing Standard, identity and lineage; the protocol owns only the composition required to make the protection operable for its governed purpose.

GOV-01-P07 --- Governed retrieval minimises unnecessary retrieval breadth while preserving context required for correct interpretation.

GOV-01-P08 --- Sophisticated governance should produce simple execution through structured knowledge, defaults, automation and proportional controls.

GOV-01-P09 --- A distinct governance concern does not automatically justify a distinct governance artefact.

GOV-01-P10 --- There is a deliberate separation between innovation and embedment: AEA Governance does not govern creativity, novelty, contradiction, exploration or experimentation merely because they exist.

GOV-01-P11 --- Governance is engaged when governed consequence is intentionally sought through submission for structured alignment, or when previously ungoverned activity is discovered or reasonably suspected to have acquired or materially threatened governed consequence.

GOV-01-P11A --- Governed consequence exists where an action, decision, state, relationship, dependency, reliance, obligation, baseline, implementation or use creates, changes, removes or materially threatens a condition protected by an applicable Governance proposition. Determination is made from the consequence and applicable protection, not from the novelty, maturity or formality of the originating thinking.

GOV-01-P12 --- Intentional submission for alignment does not presume that a change exists; alignment determines the relationship between the matter presented and the governed context before an appropriate governed treatment is selected.

GOV-01-P13 --- Governance scales with the consequence of the proposed, actual or materially threatened embedment rather than with the novelty or maturity of the idea.

GOV-01-P14 --- Innovation remains subject to applicable legal, contractual, IP, privacy, security and other obligations; freedom from AEA change governance is not freedom from all governing conditions.

GOV-01-P15 --- Governed progression is not assumed to be linear. AEA permits recursive, concurrent and interacting loops while preserving architectural ownership and consequence boundaries.

GOV-01-P16 --- A loop remains within the governance conditions of its current context until its output intentionally crosses, actually crosses, or is reasonably suspected to have crossed a boundary carrying different governed consequence.

GOV-01-P17 --- Governance may be triggered by a change in consequence even where the governed object, its content or its lifecycle condition has not changed.

GOV-01-P17A --- An applicability determination is valid only while the material conditions on which it was made remain true. A material change in audience, use, scale, dependency, reliance, authority, rights, contract, baseline, environment or other consequence-bearing condition triggers reassessment to the extent affected; absence of change does not require ceremonial re-determination.

GOV-01-P18 --- Preparation for a governed condition does not constitute attainment of that condition.

Information required

At system level the Governance System must be able to establish: the governed concern; proposition identity; semantic owner; applicability; parent and specialisation lineage; applicable Design relationship; governing authority; lifecycle state; dependencies; relevant profiles; conformance expectations; and material provenance.

Use

GOV-01 is used whenever a new governance rule, profile, protocol, Standard, exception or specialised mechanism is proposed. The first question is not "where should this document live?" but:

At what level is this rule actually true, and what already governs it?

Construction rules

A proposed new parent Governance concern must demonstrate a universal governance phenomenon that cannot be coherently owned by an existing parent concern. Additional detail, implementation complexity or a large volume of content is not sufficient justification.

A profile is created to specialise inherited governance for a bounded context. It must identify the inherited propositions it specialises and the delta it introduces. Where applicable specialisations conflict, the conflict is resolved as a governed determination rather than by document order, implementation convenience or silent precedence.

Protection protocols may compose governing propositions for operational use. Composition must preserve proposition identity, semantic ownership, lineage, applicability and any conditions on permitted specialisation.

Conformance

A Governance System conforms to GOV-01 when its material rules have clear ownership and applicability, specialisations retain lineage, contradictions are governed rather than hidden, and consumers can traverse from an applied rule back to its governing proposition.

Illegal moves

Creating a child governance regime that silently replaces its parent; copying rules until their authority becomes ambiguous; creating a new Standard merely because a topic is complicated; or requiring users to infer precedence from folder position are non-conforming moves.


GOV-02 --- Governance Object & Record Standard

Purpose and boundary

GOV-02 defines the kinds of things Governance governs and the minimum semantic distinctions required to manage them correctly. It owns object and record semantics, not the subject-specific content of every object.

Governing propositions

GOV-02-P01 --- Governed object identity is distinct from its representation, location and current condition.

GOV-02-P02 --- A governed record captures required information about a governed object or governance event; the record is not automatically the object itself.

GOV-02-P03 --- A register is normally a render of governed information, not the underlying information model.

GOV-02-P04 --- A render may also be an evidence-bearing or legally significant record where that status is explicitly established; where so established, the exact evidence-bearing representation must be reproducible or fixed as required by its reliance context.

GOV-02-P05 --- Canonical propositions must be atomic enough to address and govern, but context-sufficient enough to interpret correctly.

GOV-02-P06 --- Composition assembles canonical objects for a purpose and does not transfer source architectural ownership.

GOV-02-P07 --- A Render assembles architectural truth; it does not manufacture it.

GOV-02-P08 --- Governed artefact families may have specialised anatomy inherited from common object/record requirements.

GOV-02-P09 --- Exploratory material does not become a governed AEA object merely because it is stored, structured, discussed or machine-readable.

GOV-02-P10 --- Material intentionally submitted for structured alignment becomes subject to the minimum governed information needed to determine its relationship to the destination context without presuming canonical or change status.

GOV-02-P11 --- Embedment occurs when material is incorporated into, made operative within, or relied upon as part of a governed object, mechanism, baseline, implementation, decision or other governed context such that its presence or removal has governed consequence.

GOV-02-P12 --- Accidental or unauthorised embedment does not acquire legitimacy from occurrence; it must be identifiable as an event requiring containment, determination and appropriate remediation.

GOV-02-P13 --- Where an object splits, merges or converges, lineage alone is insufficient: propositions, evidence, decisions, dependencies and unresolved conditions must be allocated to the resulting identities to the extent required for semantic responsibility.

Information required

Governed objects require, as applicable: identity; object class; semantic owner; canonicality; status; version/baseline context; applicability; authority; relationships; provenance; evidence relationships; representation/render relationships; and qualification.

Records additionally require the event/state evidenced, time/context, actor or mechanism, applicable authority and integrity/retention conditions where material.

Use

GOV-02 is the classification point before lifecycle, identity, release, repository or conformance controls are applied. If the system cannot say what kind of governed thing it is dealing with, downstream controls are likely to be wrong.

Construction rules

New object classes are introduced only where they create a governance consequence that cannot be represented through an existing class plus attributes/relationships. Technical table design must not become the ontology by accident.

Conformance

A consumer must be able to distinguish current canonical knowledge from a record, derivative, composition, render, source or historical representation without relying on guesswork.

Illegal moves

Treating every file as a distinct governed object; treating every database row as a proposition; assuming every render is non-evidentiary; or making object classes mirror repository folders.


GOV-03 --- Identity & Addressing Standard

Purpose and boundary

GOV-03 ensures that governed objects remain identifiable and resolvable across change, representation, repository movement and time.

Governing propositions

GOV-03-P01 --- Identity persists independently of location, representation and version.

GOV-03-P02 --- Canonical identifiers are never reused for a different governed object.

GOV-03-P03 --- A change of location, repository, render or publication does not by itself create a new governed identity.

GOV-03-P04 --- A material change in meaning may require a new identity or explicit supersession rather than silent mutation.

GOV-03-P05 --- Alias, shorthand and human-friendly names must resolve to the governed identity without obscuring the identity requested, the identity resolved, or material ambiguity.

GOV-03-P06 --- Working or exploratory identifiers may exist without being canonical identifiers; entry into a governed dependency, release or canonical relationship requires the identity conditions appropriate to that consequence.

GOV-03-P07 --- Split and merge events preserve predecessor/successor lineage and must not erase historical identity.

GOV-03-P08 --- Recovery from corruption or loss must re-establish identity from governed evidence rather than infer identity from restored file names or locations.

Information required

Identity records require: persistent identifier; object class; current canonical reference; aliases; status; identity-event history; predecessor/successor relationships; and resolver information where applicable.

Use

Identity is established before a governed object is depended upon by other governed objects. Cross-references should use logical identity rather than fragile physical paths wherever practical.

Construction rules

The exact identifier grammar remains governed by this Standard and its applicable conventions. Identifier syntax must support stability and machine resolution without embedding volatile meaning that forces renumbering when organisational structure changes.

Insertions must not require renumbering existing propositions. Deprecated identities remain historically resolvable.

Conformance

A conforming identity scheme can answer: "Which exact governed thing is this?", "Has it changed identity?", "What replaced it?", and "Can I still resolve an old reference?"

Illegal moves

Reusing IDs; renumbering the estate to make it visually neat; embedding mutable folder hierarchy into identity; or silently merging duplicates without preserving aliases and lineage.


GOV-04 --- Authority & Decision Governance Standard

Purpose and boundary

GOV-04 defines authority semantics and governs which authority may make, approve, activate, hold, access or delegate governed decisions and actions. Trust may determine whether reliance is warranted; it does not itself create authority.

Governing propositions

GOV-04-P01 --- Authority is a governed permission or accountability to determine, approve, direct, use, activate or act within a defined scope and condition; technical capability or access is not authority.

GOV-04-P02 --- Authority classes include Canonical Architectural Authority, Decision Authority, Approval Authority, Custody Authority, Access Authority, Information Use Authority, Action Authority, Activation Authority and Delegated Authority where applicable.

GOV-04-P03 --- Authority must be explicit enough to establish subject, scope, action/decision permitted, conditions, delegation if any, and temporal applicability.

GOV-04-P04 --- Canonical Architectural Authority governs authoritative architectural determination but does not bypass applicable identity, provenance, integrity, lifecycle, release or assurance requirements merely by making a ruling.

GOV-04-P05 --- An authoritative ruling is authoritative input to the applicable governed mechanism unless an existing governing proposition explicitly grants direct effect for a bounded consequence and establishes the minimum conditions under which that direct effect is lawful.

GOV-04-P06 --- The authority to define permitted lifecycle transitions is distinct from the authority to approve or cause a particular transition occurrence.

GOV-04-P07 --- Where one person holds multiple authorities, the governance record must preserve which authority was exercised for each material consequence; identity of the person alone is insufficient.

GOV-04-P08 --- Delegated authority must be bounded, traceable and revocable; delegation does not transfer the delegator's broader authority.

GOV-04-P09 --- Agents and machines may execute delegated actions or use information only within explicitly established authority and reliance conditions; access, retrieval or technical capability does not imply decision or canonical authority.

GOV-04-P10 --- Emergency action may use a specialised expedited mechanism, but must preserve minimum invariants of identity, authority exercised, reason, consequence, evidence, temporary condition where applicable, and retrospective reconciliation.

Information required

Authority information may include authority class; holder; subject/scope; permitted actions/decisions; conditions; delegation source; start/end or lifecycle; revocation; evidence; and relationship to applicable Trust/Reliance conditions.

Use

Before a material governed action, the system determines which authority class is required, whether it is held or validly delegated, and whether any additional approval or reliance condition applies.

Construction rules

Do not instantiate every authority class on every object. Use only classes that create a governance consequence. Machine-enforced permissions may implement authority conditions but do not define them.

Conformance

A conforming decision can establish why the actor/mechanism was authorised for that consequence at that time.

Illegal moves

"Admin therefore owner"; "AI can therefore AI may"; treating approval as canonical authorship; or letting a delegated actor expand its own delegation.


GOV-05 --- Source & Provenance Governance Standard

Purpose and boundary

GOV-05 preserves the origin, evidentiary lineage and influence of knowledge without confusing provenance with authority.

Governing propositions

GOV-05-P01 --- A Source may inform AEA without becoming AEA doctrine or acquiring canonical authority.

GOV-05-P02 --- Provenance records where knowledge, evidence or contribution came from; provenance is not authority.

GOV-05-P03 --- Authoritative Source or source-of-truth designation must be distinguished from the Ecosystem Source actor and from Canonical Architectural Authority.

GOV-05-P04 --- Material propositions retain traceable lineage to source evidence, owner rulings and predecessor propositions where applicable.

GOV-05-P05 --- Evidence fitness is use-specific; the existence of evidence does not establish that it is sufficient for every reliance context.

GOV-05-P06 --- External contribution conditions are established through applicable Ecosystem/contractual mechanisms; Governance consumes those conditions rather than inventing them.

GOV-05-P07 --- Where contractual meaning is ambiguous, Governance preserves the applicable condition and routes interpretation to appropriate legal/commercial authority.

GOV-05-P08 --- Temporal provenance preserves which agreement, source, version or condition governed an exchange where material.

GOV-05-P09 --- Material entering structured alignment preserves enough provenance to distinguish observation, source evidence, inference, proposition, experimental result and authoritative ruling where those distinctions affect determination.

GOV-05-P10 --- Independent recurrence must not be erased merely because separately originating observations or ideas converge on the same proposition.

GOV-05-P11 --- Re-entry after rejection, hold or return must retain prior rationale and identify materially changed evidence, context or interpretation where applicable.

GOV-05-P12 --- A non-inference condition travels with material and derived use until an authorised governing determination explicitly establishes what inference is permitted; transformation alone does not extinguish the restriction.

Information required

Source identity; source class/relationship; provenance link; date/context; evidence relationship; applicable use conditions; confidence/qualification where relevant; and the canonical objects materially informed.

Use

GOV-05 is used during research intake, candidate development, canonical drafting, evidence assessment, publication and assurance.

Construction rules

Do not create a different Source type for every origin. Add taxonomy only where different treatment is required. "Authoritative Source" refers to a designated source for a defined information purpose and must not be used as shorthand for Canonical Architectural Authority.

Conformance

A material proposition's provenance can be established without a consumer mistaking the Source for the proposition's governing authority.

Illegal moves

Copying external material into canon without provenance; treating citations as approval; deleting source lineage because wording was rewritten; or calling every useful source authoritative.


GOV-06 --- Intellectual Property Governance Standard

Purpose and boundary

GOV-06 governs ownership, rights, permitted use, disclosure, contribution and derivative conditions for AEA intellectual property and AEA-derived material.

Governing propositions

GOV-06-P01 --- Participation in building, implementing, selling or proving AEA-derived work does not by itself create ownership of AEA IP or broader commercial rights.

GOV-06-P02 --- Canonical AEA IP remains distinguishable from commercial wrappers and downstream participation rights.

GOV-06-P03 --- Publication is controlled disclosure and must preserve the public/internal/proprietary boundary applicable to the material.

GOV-06-P04 --- Public disclosure must be sufficient to define, implement and independently conform to AEA without requiring disclosure of proprietary methods that are not necessary for conformance.

GOV-06-P05 --- Derivative works and contributions require explicit provenance and applicable rights conditions.

GOV-06-P06 --- Third-party IP must remain distinguishable from AEA-owned doctrine and from permitted use of external Sources.

GOV-06-P07 --- Governance records and enforces established IP conditions; it does not invent or interpret unresolved legal ownership terms.

GOV-06-P08 --- Commercial wrappers may have independent ownership, licensing or transfer arrangements without automatically transferring canonical AEA IP.

GOV-06-P09 --- Where external or partner material is submitted for structured alignment, applicable contribution, confidentiality, derivative-use and incorporation conditions must be established before substantive incorporation or use where those conditions are material.

GOV-06-P10 --- Architectural validity does not override external contractual, regulatory, IP or commercial conditions that lawfully constrain embedment; a determination may therefore be architecturally valid but not currently embeddable.

Information required

IP owner; IP class; rights granted/reserved; licence or contractual basis; contribution source; derivative relationship; disclosure classification; attribution requirements; third-party conditions; confidentiality; and relevant temporal agreement/version context.

Use

GOV-06 applies before publication, licensing, external contribution incorporation, partner access, commercial wrapper creation and transfer/sale of derivative businesses or products.

Construction rules

Do not encode commercial assumptions as permanent IP doctrine. Separate canonical ownership from granted participation rights and wrapper-specific arrangements.

Conformance

A consumer can establish what IP is being used, who owns it, under what right it is being used or disclosed, and whether derivative/contribution conditions have been satisfied.

Illegal moves

Assuming a development partner owns what it builds merely because it built it; publishing proprietary method because the underlying Standard is public; or letting a commercial wrapper silently acquire canonical IP.


GOV-07 --- Lifecycle & Status Standard

Purpose and boundary

GOV-07 governs the meaningful states of governed objects and the evidence required for transitions between them. It does not own version numbering or release mechanics.

Governing propositions

GOV-07-P01 --- Lifecycle describes the governed condition of an object and the permitted transitions associated with that condition; it does not prescribe one universal linear workflow.

GOV-07-P02 --- Different governed contexts may use different lifecycle vocabularies and specialised conditions where their semantics remain explicit and interoperable at consequence boundaries.

GOV-07-P03 --- Governed lifecycle may include advance, return, pause, hold, re-entry, split, merge, convergence, supersession, rejection, withdrawal and termination without implying that every object must support every transition.

GOV-07-P04 --- A materially governed transition must resolve the source context/condition, destination context/condition, affected identity, consequence gained/lost/changed, required authority, evidence of lawful occurrence, provenance/lineage, dependency consequence, assurance consequence, unresolved qualifications and reversibility/return conditions where material.

GOV-07-P05 --- An object may participate concurrently in multiple governed lifecycle contexts; those conditions must remain dimensionally distinguishable rather than flattened into one status.

GOV-07-P06 --- The semantics of a permitted transition are governed separately from the authority to approve or cause a particular transition occurrence.

GOV-07-P07 --- Re-entry does not erase prior lifecycle history, rationale or unresolved conditions.

GOV-07-P08 --- Partial outcomes are legitimate: part of a matter may progress to one governed destination while another part is held, rejected, returned or embedded elsewhere, provided identities and consequence remain legible.

GOV-07-P09 --- A change in audience, scale, dependency, reliance, contract or external condition may alter governed consequence without changing lifecycle state and may require reassessment.

GOV-07-P10 --- Preparation for, representation of, or expectation of a lifecycle transition does not establish that the transition occurred.

GOV-07-P11 --- Lifecycle terminology used by specialised contexts must not be treated as a universal AEA ontology unless explicitly governed as such.

Information required

Object identity; lifecycle dimension; current state; permitted transitions; transition authority; transition evidence; effective time; prior state; qualification; and applicable specialised state model.

Use

Lifecycle is evaluated before use, publication, implementation, change, conformance and retention decisions.

Construction rules

New states must demonstrate a distinct governance consequence. Avoid multiplying near-synonymous states to describe workflow convenience.

Conformance

A consumer can determine the object's current governed state, what that state permits, and how it reached that state.

Illegal moves

Using status as identity; inventing "approved-ish" states with no defined consequence; silently changing state; or treating archived as synonymous with invalid.


GOV-08 --- Change Management Standard

Purpose and boundary

GOV-08 governs how observations and proposed changes enter, are assessed, decided, implemented and returned to the governed system. It owns change governance, not the semantic subject matter being changed.

Governing propositions

GOV-08-P01 --- Governed change is a mechanism for assessing and controlling proposed or discovered alterations to governed consequence; it is not the lifecycle itself.

GOV-08-P02 --- The normal deliberate path begins when material is intentionally submitted for structured alignment because governed embedment is being considered.

GOV-08-P03 --- Structured alignment must establish, at minimum, the matter presented, relevant governed context, provenance, current understanding, material uncertainty, intended or suspected consequence, and the determination or next governed treatment; it must not presume that a change exists.

GOV-08-P04 --- Alignment may determine that a matter is already represented, a clarification/articulation, evidence, local implementation choice, composition, contextual treatment, variant, specialisation, extension, actual governed change, unresolved matter, or material requiring further exploration; exact disposition vocabulary may be specialised and is not fixed here.

GOV-08-P05 --- A Change Candidate exists only when governed determination establishes that alteration of a governed object or governed consequence is actually being proposed or required.

GOV-08-P06 --- Governance must also accept a detected-consequence path when previously ungoverned activity is discovered or reasonably suspected to have acquired or materially threatened governed consequence, regardless of whether the originating idea was intentionally submitted or sufficiently formed.

GOV-08-P07 --- Accidental or unauthorised embedment must be contained and retrospectively determined without being legitimised by use, popularity, success or duration.

GOV-08-P08 --- Change treatment must be proportionate to consequence and may return, hold, split, merge, consolidate, reject, accept, condition, defer, withdraw, remediate or route a matter as appropriate without requiring linear progression.

GOV-08-P09 --- Local improvement remains local only while it stays within the consequence boundaries of the applicable governed context; changing a canonical invariant contract, evidence/control obligation, relied-upon output, supported baseline or equivalent governed condition requires the appropriate escalation.

GOV-08-P10 --- A valid embedment may later require reversal, withdrawal, migration or de-embedment; removal is itself governed where it changes dependencies, reliance, evidence, baseline or other consequence.

GOV-08-P11 --- Finding closure is distinct from remediation completion and from removal of consequence; each must remain separately legible where material.

GOV-08-P12 --- Return for further exploration must record enough rationale to distinguish legitimate uncertainty or learning need from avoidance of a required governance determination.

GOV-08-P13 --- Owner or canonical-authority rulings enter change governance according to their governed effect and do not silently mutate canon.

Information required

Candidate identity; trigger/source; observation; proposed change; affected object; defect classification; evidence; materiality/risk; dependencies; authority; decision; rationale; disposition; implementation/release relationships; return-path status; and history.

Use

GOV-08 is the controlled bridge between learning and canonical change.

Construction rules

T-shirt sizing may be used to scale controls where the applicable governance profile establishes it. Low-consequence changes should not be forced through heavyweight ceremony designed for high-consequence change.

Conformance

Every material canonical change can be traced to a governed candidate/decision path and its consequence assessment.

Illegal moves

Editing canon because "everyone agrees"; merging candidates until recurrence disappears; treating rejection as deletion; or assuming an approved change has propagated everywhere.


GOV-09 --- Dependency, Blast Radius & Integrity Standard

Purpose and boundary

GOV-09 governs material dependency relationships, consequence assessment and integrity of the governed set when change occurs.

Governing propositions

GOV-09-P01 --- Dependency is a governed relationship through which change or failure in one object may affect another; dependency does not itself establish warranted reliance.

GOV-09-P02 --- Blast-radius assessment identifies reasonably foreseeable direct and inherited consequences of a proposed, actual or discovered change.

GOV-09-P03 --- Integrity assessment must consider explicit dependencies and material unknown or suspected dependencies where uncertainty itself affects consequence.

GOV-09-P04 --- Newly discovered dependency, audience, scale, reliance or external condition may trigger consequence reassessment even when no object changed and no lifecycle transition occurred. A prior applicability or non-applicability determination remains authoritative only while the material conditions supporting it remain true.

GOV-09-P05 --- Material new information discovered during assessment reopens or extends assessment to the extent necessary; prior completion does not immunise the decision from changed consequence.

GOV-09-P06 --- Partial embedment, split, merge, convergence, rollback and de-embedment require dependency consequences to be allocated to the resulting or affected objects rather than inherited indiscriminately.

GOV-09-P07 --- Continuing non-adoption of a current canonical baseline may be legitimate where the applicable authority, rationale, conditions, review point and affected dependencies are explicit.

GOV-09-P08 --- Integrity collisions must distinguish at least contradiction, incompatible applicability, unresolved dependency, stale baseline, identity ambiguity, provenance conflict and unauthorised embedment where those distinctions change treatment.

GOV-09-P09 --- A composition or implementation may depend on more than one supported baseline or specialised profile; applicability must be resolvable proposition-by-proposition or dependency-by-dependency where a single baseline label would be false.

GOV-09-P10 --- Blast-radius completion does not imply all remediation or migration has completed; residual exposure remains explicit until consequence is actually resolved.

Information required

Source and target identities; dependency type; materiality; direction; baseline/context; consequence if source changes; propagation status/disposition; authority; evidence; review condition; and uncertainty about completeness where material.

Use

GOV-09 is invoked during material change, release, assurance, architecture extension and conformance assessment.

Construction rules

Dependency taxonomy should distinguish relationships only where they alter consequence or traversal. Do not create relationship labels solely to make diagrams richer.

Conformance

A material change can demonstrate how known affected dependencies were assessed and what happened to each, while acknowledging the residual risk of unknown dependency.

Illegal moves

"Graph says zero impact"; forced upgrade as the only propagation outcome; treating a cross-reference as automatically material dependency; or ignoring a dependent implementation because it is on an older baseline.


GOV-10 --- Version, Release & Publication Standard

Purpose and boundary

GOV-10 governs versions, governed baselines, release and controlled publication/exposure. It distinguishes canonical evolution from implementation adoption and public disclosure.

Governing propositions

GOV-10-P01 --- Version identifies a governed revision; release establishes a governed baseline available for its defined use; publication is a controlled representation/disclosure of governed content. These are distinct events.

GOV-10-P02 --- A released baseline is immutable as a released baseline. Correction requires a new governed release or explicit withdrawal/supersession mechanism rather than silent alteration.

GOV-10-P03 --- Current canon does not automatically invalidate prior supported implementation baselines.

GOV-10-P04 --- Propagation requires consequence assessment across affected consumers and dependencies; it does not require universal synchronisation.

GOV-10-P05 --- Support, compatibility and applicability are contextual and time-bounded conditions rather than inherent properties of version number alone.

GOV-10-P06 --- Embedment is not synonymous with release, publication or canonicalisation; material may be validly embedded into another governed destination without becoming canon.

GOV-10-P07 --- Withdrawal of a publication changes the availability or permitted reliance on that publication but does not by itself erase the underlying canonical object, historical release or evidence of prior publication.

GOV-10-P08 --- Human and machine renders claiming the same baseline must resolve to semantically aligned governed content and expose material qualifications consistently.

GOV-10-P09 --- Evidence-bearing renders must preserve the exact representation or reproducibility conditions required by the evidence/reliance context.

GOV-10-P10 --- Recovery of release state must prove identity, content integrity, authority, history and dependency state from governed evidence rather than merely restore repository files.

Information required

Object/version identity; version relationship; release/baseline identity; canonical/non-canonical status; effective context; branch/backport relationship; publication audience/classification; derivative relationship; supersession; approval authority; release evidence; and implementation support/reliance context where applicable.

Use

GOV-10 governs publication of Standards, machine-readable releases, public derivatives, internal releases, supported baselines and controlled backports.

Construction rules

Semantic versioning may be used where established by the applicable profile, but numbering conventions must not substitute for explicit governance meaning. Support/compatibility may be contextual and time-bound rather than a universal property of a baseline.

Conformance

A consumer can establish exactly which governed baseline it is using, whether that baseline is canonical or derivative, its currency for the intended context and the applicable publication/disclosure conditions.

Illegal moves

Calling every save a version; equating "latest" with "applicable"; allowing a backport to masquerade as canon; or publishing because release approval happened to exist.


GOV-11 --- Information, Schema & Machine-Readability Standard

Purpose and boundary

GOV-11 governs the semantic information requirements and representations that allow Governance knowledge to be stored, traversed, exchanged and reasoned over by humans and machines.

Governing propositions

GOV-11-P01 --- Governed information must be structured sufficiently for human and machine consumers to distinguish identity, authority, currency, applicability, provenance, uncertainty and relationships required for correct use.

GOV-11-P02 --- Machine readability does not transfer authority to a schema, repository, model or automation.

GOV-11-P03 --- Canonical, non-canonical, exploratory, aligned, candidate, superseded and other materially different governance conditions must be machine-distinguishable where their confusion could change consequence; these distinctions are semantic conditions and not automatically universal lifecycle states.

GOV-11-P04 --- Machine consumers must preserve material uncertainty, qualification and non-inference conditions rather than silently resolve them into certainty.

GOV-11-P05 --- Retrieval must prefer applicable authoritative propositions and expand to context, relationships, evidence and history only as required for correct interpretation.

GOV-11-P06 --- Where non-canonical material is permitted to inform machine reasoning, the permission, purpose and resulting influence must remain distinguishable enough to prevent synthesis from being represented as canonical AEA.

GOV-11-P07 --- Metadata labels alone are insufficient where search, preview, export, copying, context assembly or transformation can strip or obscure governance condition; controls must preserve semantic condition through those operations.

GOV-11-P08 --- A machine-generated derivative does not inherit canonical authority merely because its inputs included canon.

GOV-11-P09 --- Alias resolution and retrieval must expose material distinction between the identity requested and the canonical identity resolved.

GOV-11-P10 --- The information model must support concurrent lifecycle/context conditions without collapsing them into one status field.

GOV-11-P11 --- Implementation schemas may specialise the information model but must not redefine architectural meaning merely for technical convenience.

Information required

Proposition/object identity; type; semantic owner; status; authority; applicability; baseline; relationships; provenance; qualification; conformance requirements; representation links; and retrieval/context metadata required by consequence.

Use

GOV-11 underpins the future canonical proposition store, knowledge graph, machine corpus and LLM access layer.

Construction rules

Do not build the schema before the semantic requirements stabilise. Technical schemas may specialise for storage/exchange but must map back to canonical semantics. Avoid dynamic convenience fields that silently acquire governance meaning.

Conformance

A machine consumer can distinguish current canonical propositions from candidates, sources, renders and history and can traverse material relationships without relying on document-order inference.

Illegal moves

Schema colonising architecture; null meaning "false"; search ranking meaning "authoritative"; or stuffing whole documents into context because proposition-level retrieval was not designed.


GOV-12 --- Assurance & Conformance Standard

Purpose and boundary

GOV-12 governs how warranted claims are made that governed objects, systems, implementations or applications satisfy applicable governance requirements.

Governing propositions

GOV-12-P01 --- Conformance is a scoped, evidence-based determination against identified applicable requirements; it is not a general declaration that a subject is good, safe or trustworthy.

GOV-12-P02 --- A conformance claim identifies subject, scope, applicable baseline or proposition set, evidence, authority, date/period, qualifications and material exclusions.

GOV-12-P03 --- Conformance does not itself create warranted reliance; Trust Architecture owns the conditions under which reliance between parties is warranted.

GOV-12-P04 --- Experimentation, repeated success or popularity may create factual reliance but does not by itself create warranted reliance or conformance; where factual reliance emerges, Governance must make the condition visible and route the consequence to the applicable governance and Trust mechanisms.

GOV-12-P05 --- A material change in baseline, dependency, audience, scale, evidence or reliance context may affect the currency of a prior conformance determination even when the conformed object has not changed.

GOV-12-P06 --- Assurance independence is determined by authority, incentives, evidence access and separation of decision function, not merely by whether the assurer is external.

GOV-12-P07 --- Agents or automated assurance mechanisms may perform bounded checks under defined reliance conditions but must not self-approve beyond delegated authority or collapse evidence generation and approval where separation is required.

GOV-12-P08 --- A finding may be closed administratively while remediation, migration, de-embedment or residual exposure remains open; assurance records must distinguish these conditions.

GOV-12-P09 --- Known defects, unresolved conditions or evidence gaps may qualify or restrict reliance pending resolution rather than forcing false binary conformance.

GOV-12-P10 --- Publication and documentation must be sufficient for an independent conforming party to determine applicable requirements without access to undisclosed proprietary methods not required for conformance.

GOV-12-P11 --- Assurance should provide sufficient confidence for the consequence involved and should not add control where additional assurance no longer materially improves confidence.

Information required

Conformance subject; scope; governing baseline/propositions; test/method; evidence; assessor; authority; independence dimensions where applicable; exceptions; qualification; result; date; validity/review period where relevant; and linked remediation/change candidates.

Use

GOV-12 supports Standard publication QA, implementation conformance, partner/certification mechanisms, machine QA and future independent audit.

Construction rules

Assurance methods should target meaningful failure modes. Do not add controls merely because they are easy to count. Automated assurance must preserve the authority and reliance conditions under which its outputs may be used.

Conformance

A third party can reconstruct what the claim actually means and what evidence justifies it.

Illegal moves

"Passed checklist therefore conforms"; second LLM equals independent review; hiding exceptions in notes; or treating assurance evidence as permanent despite material baseline change.


GOV-13 --- Repository, Access & Retention Standard

Purpose and boundary

GOV-13 governs custody, storage, access, persistence, retrieval and retention of governed knowledge and records. It does not determine canonical semantic truth.

Governing propositions

GOV-13-P01 --- Repository location is custody, not canonical authority; file presence does not establish truth, status or permission.

GOV-13-P02 --- Access is distinct from authority, information-use permission, contractual right and IP entitlement.

GOV-13-P03 --- Access revocation does not by itself terminate contractual, licensing or other rights, and rights termination does not by itself prove technical access has been revoked; each applicable mechanism must be governed independently and reconciled where required.

GOV-13-P04 --- Retention and disposal preserve legal, evidentiary, historical, provenance and supersession obligations applicable to the governed object or record.

GOV-13-P05 --- Exploratory and governed material may coexist in infrastructure only where governance condition remains unambiguous through storage, search, preview, export, copying, retrieval and machine context assembly; otherwise separation or additional controls are required.

GOV-13-P06 --- A sandbox, working area, repository branch, folder or system does not create or alter governance status merely by location or naming.

GOV-13-P07 --- Repository recovery must restore more than files: governed identity, release integrity, authority evidence, history, access condition and dependency state must be reconstructable.

GOV-13-P08 --- Repository automation must not publish, promote, canonicalise or otherwise change governed consequence merely because a technical condition was met unless the required governance authority and transition conditions are also satisfied.

GOV-13-P09 --- Archive status does not erase unresolved consequence, active rights, evidence obligations or historical applicability.

Information required

Custody location; repository; object identity; access classification; authorised users/mechanisms; enforcement mode; retention requirement; archival state; integrity evidence; backup/recovery where material; physical representation/path; and logical resolution relationship.

Use

GOV-13 applies to the canonical AEA repository, working areas, archives, machine-readable stores, release locations and evidence repositories.

Construction rules

Repository structure should optimise operational custody and navigation without duplicating the ontology. Working areas must remain distinguishable from authoritative custody locations and published releases.

Conformance

A governed object can be located, accessed by authorised consumers, retained for the required period and moved without losing identity, history or semantic authority.

Illegal moves

Folder equals ontology; write permission equals decision authority; archive equals deletion; or calling a repository "source of truth" without clarifying whether the claim concerns custody or semantic authority.


v1.0.0 NORMATIVE RECONCILIATION --- PROTECTION, APPLICABILITY AND CONSEQUENCE

The following propositions are normative Governance requirements derived from the companion AEA Governance System Design v1.0.0. They supersede conflicting earlier working wording. Architectural observations and lens-specific rationale remain in the Design; these propositions state what Governance requires.

GOV-01 --- system and protection model

GOV-01-P19 --- Governance is not an Architecture within the AEA Architecture Set. Governance is a governing system applicable to any subject or context in which governed consequence exists.

GOV-01-P20 --- Governance standardises protection, not implementation. A protection is established once at the highest level at which its protective intent is universally valid and is inherited wherever applicable. Implementation may be specialised for context without defeating the inherited protection.

GOV-01-P21 --- A Governance Standard is the canonical owner of one or more governing protections within its semantic concern. A protection protocol is the applicable expression of those protections for a governed subject. A profile or specialisation resolves contextual requirements. An implementation mechanism realises them operationally. These are related but not interchangeable objects.

GOV-01-P22 --- Protection applicability is consequence-based and must be determinable. Material non-applicability must be explicit where omission could otherwise be mistaken for satisfaction or oversight.

GOV-01-P23 --- Where inherited specialisations conflict, resolution must preserve the protective intent and constraints of all applicable parent protections unless authorised variation is explicitly permitted. Document location, local convenience or arbitrary hierarchy does not resolve the conflict.

GOV-01-P24 --- The same protection protocols may apply across canonical AEA, AEA Design, AEA in Action, BOAS, commercial wrappers, products, software, SKUs, customer implementations, publications, machine/agent implementations and other governed subjects; their implementation need not be identical.

The common protection spine includes, where applicable: coherent identity; explicit authority; provenance and lineage; lifecycle condition; controlled consequential transition; dependency and consequence assessment; assurance proportionate to consequence; rights and obligations; baseline/release integrity; retrievability; and preservation of material history. This list identifies protected concerns, not a universal implementation checklist.

GOV-02 / GOV-03 --- governed handoff continuity

GOV-02-P13 --- Once a subject is intentionally handed into governed consideration, Governance creates or acknowledges a stable governed reference to the form submitted, its originating context, material provenance/restrictions and handoff time. This is a post-handoff protection and not an upstream innovation qualification rule.

GOV-03-P11 --- Return to innovation, material alteration and re-entry must preserve sufficient lineage to determine whether the returning matter is continuation of the governed subject, a derivative of it, or a materially new submission. Split and merge events preserve predecessor/successor relationships without reusing identity.

GOV-04 --- determination and portfolio authority

GOV-04-P14 --- Activity and evidence do not constitute progression. A consequential transition requires a governed determination preserving its basis, applicable authority where required, resulting governed condition and permitted next treatment.

GOV-04-P15 --- Portfolio visibility does not transfer authority. Portfolio-level findings may inform or constrain item-level determinations only through an applicable governing relationship whose basis and currency are preserved.

GOV-07 --- non-progression and durable determinations

GOV-07-P14 --- Non-progression is a legitimate governed outcome. Hold, return, rejection, termination, redirect and equivalent specialised outcomes retain material rationale and evidence while remaining distinguishable from current governing direction.

GOV-07-P15 --- A governed determination to retain an existing baseline or configuration may remain valid without repeated reconsideration while its stated conditions continue to hold. Material triggers or changed conditions may reopen the determination.

GOV-08 --- governed consideration and destination routing

GOV-08-P11 --- Normal entry into governed consideration is initiated by intentional handoff from the originating context. Governance does not prescribe how innovation determines readiness for submission. Proofs, prototypes, experiments and exploratory evidence may accompany handoff but are not universal Governance entry gates.

GOV-08-P12 --- Submission does not presume a Change Candidate. Alignment first determines the relationship between the submitted matter and the governed context; only then is the appropriate governed treatment selected.

GOV-08-P13 --- One submitted matter may produce multiple governed destinations. Each destination requires its own applicable protection composition, authority, evidence and consequential determination.

GOV-08-P14 --- Where downstream consequence assessment determines that a governed destination should change, that conclusion must enter the applicable governed change mechanism for that destination. Assessment does not itself authorise mutation.

GOV-09 --- portfolio, blast radius and downstream consequence

GOV-09-P13 --- Portfolio scope is bounded by relevant dependency and consequence. Individually minor matters must be reconsidered collectively where cumulative consequence becomes material. Material portfolio assumptions or constraints require reassessment when their governing conditions materially change.

GOV-09-P14 --- Propagation is consequence assessment, not synchronisation. Source evolution identifies potentially affected downstream subjects and requires context-specific determination; it does not automatically invalidate, alter or update them.

GOV-09-P15 --- Downstream consequence determination must permit an explicit unknown or insufficiently established condition where lineage, dependency or actual state is inadequate. Uncertainty must not be forced into affected/not-affected or change/no-change.

GOV-09-P16 --- Difference from current canon is not by itself a defect, non-conformance or requirement to change. A derivative may legitimately retain an earlier baseline or deliberate mutation where it remains appropriate to its purpose, conditions, rights and obligations.

GOV-09-P17 --- Lineage must remain distinguishable from current semantic equivalence. Historical derivation may remain true even where the derivative no longer means the same thing as current source canon.

GOV-10 --- destination-specific embedment

GOV-10-P13 --- Approval is not embedment and implementation activity is not embedment. Embedment is established only when the applicable protection conditions of the governed destination have been satisfied and evidenced.

GOV-10-P14 --- The applicable embedment condition set is composed from the inherited and specialised protections relevant to the destination. Its material governing baseline must be determinable; no universal destination checklist is presumed.

GOV-11 --- machine semantics

GOV-11-P14 --- Machine-readable Governance must distinguish Governance System Design observations, normative Governance propositions, protection protocols, profiles/specialisations and implementation mechanisms. It must not infer universal AEA doctrine merely because an AEA architectural lens produced a subject-specific Governance design observation.

GOV-11-P15 --- Machine consumers must preserve uncertainty, lineage versus semantic equivalence, and the distinction between evidence, determination, approval, embedment and downstream assessment.

GOV-12 --- effective assurance

GOV-12-P13 --- Assurance tests whether the required protection is effective for the consequence involved, not merely whether a protocol, record, control or governance activity is present.

GOV-13 --- historical retrievability

GOV-13-P11 --- Historical and non-progression evidence must remain retrievable without being presented as current governing direction. Retrieval must expose sufficient lifecycle, authority and currency context to prevent stale material from masquerading as active instruction.

Publication boundary --- matters deliberately not invented

This published baseline does not lock the exact canonical AEA identifier grammar, universal lifecycle state vocabulary, propagation disposition vocabulary, certification model, technical schema, repository technology, assurance scoring model or detailed contractual/IP terms. Those remain subject to the applicable Governance Standard, profile, implementation context, owner decision or legal determination.

Cross-cutting precision requirements

The following requirements clarify the application of Governance doctrine and form part of this published baseline.

Operational performance is not architectural quality

Measures of governance-funnel operation --- including throughput, elapsed time, progression, hold, return, fallout, conversion or similar operational measures --- describe the performance or behaviour of the governing mechanism. They do not, by themselves, establish the architectural quality, correctness, fitness, authority or warranted reliance of a resulting determination.

Operational performance evidence is not architectural quality or correctness.

Retrieval does not confer currency or authority

The ability to discover or retrieve a governed proposition, determination, record, evidence item or historical state does not establish that it is current, applicable or authoritative for the intended use. Retrieval must preserve or expose sufficient identity, status, version or baseline, applicability, authority, provenance and supersession context to determine whether the retrieved knowledge may presently be relied upon.

Retrievability does not imply current applicability or authority.

Embedment is determined against an applicable governed condition set

A determination that something is embedded must identify the applicable governed conditions and baseline against which embedment was established. Later evolution of a source, Standard, protection, condition set or baseline does not retrospectively invalidate an embedment that was validly established under its applicable governed conditions, unless an applicable governing condition requires reassessment.

Embedment is assessed against the applicable governed conditions and baseline in effect for that determination.

Keep readingAEA by Ivory & Co. Governance System DesignStandards · Governance System Design →
→Continue

Where to go next.