note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

DEV-06 -- AIA Suggestion Flow

Canonical spec: 02_SKYZAI/02_ORGANISM_COMMONS/EXECUTION/SKYZAI/memory/cortex-os/06_AIA.md. Product face: 02_SKYZAI/02_ORGANISM_COMMONS/NOOSPHERE/10_AGENTS/AIA_PRODUCT/.

Boundary

AIA is the L6 gardener over Cortex. It is not the Rosetta pipeline. It is not a watchman. It is not a silent rewriter.

Cadence Flow

Cortex graph
  -> AIA cadence walk
  -> detect recommend / prune / consolidate / grow opportunity
  -> create aia_suggestion object
  -> user reads
  -> hold / approve / reject / defer
  -> stage unsigned proposal for typed authority review
  -> private act: Natural Person signs their own change
  -> public-DAV consequence: require a complete valid bound PRISM decision receipt
     from at least two natural-person councilors binding that exact consequence
  -> PRISM records and verifies that receipt only
  -> software deterministically applies only that exact bound structural change
     after validating the complete receipt
  -> write receipts to suggestion trace and touched objects

Suggestion Object

Required fields from the spec:

Field	Meaning
id	unique suggestion identifier
type	recommend, prune, consolidate, or grow
target_node_ids	semantic objects affected
rationale	source-linked justification
confidence	AIA confidence
severity	low, medium, high
status	pending, held, approved, rejected, deferred
cadence_source	daily, weekly, manual, or event-triggered
proposed_disposition	concrete change proposed
authority_receipt	null until a typed private signature or public-DAV quorum decision receipt exists
receipts	traces of accepted changes

Product Face

AIA_PRODUCT turns the gardener into principal-facing surfaces:

• BRIEF/
• DCR-PENDING/
• WATCH/
• ARCHIVE/

These are projections of the gardener, not a second AIA.

Hard Rule

Suggestions are autonomous. Structural acceptance is not. Anything that merges, archives, restructures, or changes lineage requires the applicable typed authority: every exact public-DAV consequence requires a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence; PRISM records and verifies only. A Legal Person change requires lawful external authority plus every executor required by law. A Natural Person authorizes their own private act, and agents stage unsigned proposals only.

⊙ = • x ○

K3 public-DAV authority history — 2026-07-12

K3 historical reference — not active authority

note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.

Cortex graph
  -> AIA cadence walk
  -> detect recommend / prune / consolidate / grow opportunity
  -> create aia_suggestion object
  -> user reads
  -> hold / approve / reject / defer
  -> stage unsigned proposal for typed authority review
  -> private act: Natural Person signs their own change
  -> public-DAV consequence: require ≥2-natural-person PRISM quorum receipt
  -> apply structural change only after validating that receipt
  -> write receipts to suggestion trace and touched objects

Suggestions are autonomous. Structural acceptance is not. Anything that merges, archives, restructures, or changes lineage requires the applicable typed authority: public-DAV consequence routes through natural-person PRISM quorum; a private Natural Person authorizes their own act.