# ── Blueprint metadata (machine-readable; the panel generator and the back-office builder read this block) ──
blueprint:
  aioc: "[ORG]AIOC-PC"
  parent: "[ORG]AIOC-CH"                  # example code of the Charter; each organisation writes its own Charter's code (Standard §1.7, item 13)
  full_name: "Product Core"
  organisation: "<organisation>"          # filled in each organisation's own copy
  type: "structural"
  org_aion: "[ORG]AION"
  blueprint_version: "v0.1.3"
  status: "draft"
  template:
    name: "49GAION AIOC Blueprint Template"
    version: "v1.5.0, with the unreleased v1.6.0 additions on main"
    source: "github.com/49g-holding/49GAION-aioc, template/AIOC-BLUEPRINT-TEMPLATE.md @ 1abae80"
  mother:
    name: "49GAION Product Core"
    version: "part card v1 (DRAFT)"
    source: "github.com/49g-holding/49GAION-protocol, library/cards/product-core.part-card.json and the Protocol section Product Core (§18) @ db682c4. This text is its mother blueprint, in its mother repository github.com/49g-holding/49GAION-product-core (49GAION DR-0024)"
  writing_repository: "<org>aioc-pc"
  code_project: "none: Product Core writes no code (Protocol §18, item 6.4)"
  panel_register_id: "none yet"
  capabilities:
    standard: ["Chief of Staff", "Office", "Input socket", "Panel"]
    functional: ["Product Intake", "Portfolio and Categories", "Research and Opportunity", "PRD and Feature Packages", "Design", "Partnership in Build", "Launch", "Run", "Explainers and Supporting Documents", "Product Review, Refresh or Retire", "Shared Standards"]

Blueprint · [ORG]AIOC-PC · Product Core · v0.1.3

Draft, 16 October 2026. v0.1.1, 19 October 2026: the Chief of Staff takes its COS code [ORG]CELL-COSPC (decisions/DR-0002). The mother blueprint of the Library part 49GAION Product Core, for any organisation (49GAION/DR-0024; decisions/DR-0001). It sets the structure stated in the Protocol section Product Core (§18) and the part card product-core.part-card.json v1 into the form of the 49GAION AIOC template: its card, its positions, its Cells and Pods, and each capability in four parts. Every rule rests on a 49GAION text, cited by section, or is new in this blueprint and marked New. It holds no organisation's data: no product, no category, no price, no company. Each organisation fills its own copy (§0, §2.1). Nothing here has run. Every fixed test reads NOT_RUN.

Product Core in one page

Product Core is the organisation's one product division, shared by every company the organisation runs. It is to products what the organisation's engineering AIOC is to engineering (Protocol §18, item 1).

What it owns. The what and the why of every product, across the product's whole life: design, the partnership in build, and the run. The engineering AIOC owns the how and the when (item 2).

Its head office is the CPO Office. Every product owner reports to it. It holds the intake of product work, the portfolio of products and their categories, the shared standards, the weekly product review, and the line to the engineering AIOC. Its accountable seat is a human position, the Chief Product Officer (item 3).

One product, one team. Products are split small. Each product has one team for every stage of its life, and the team stays with it: one owner position whose only job is that product, and AI members by function (item 5). Each team goes, in order, through:

1. research and opportunity;
2. the PRD and its feature packages, with acceptance criteria;
3. design: flows, a screen for every state, copy in every language the product serves;
4. partnership in build: answers, first look, acceptance criterion by criterion; never code;
5. launch;
6. run: pricing and rates, performance and profit and loss, communications and retention, customer voice and complaints, operations;
7. explainers and supporting documents;
8. refresh or retire.

What it never does. It writes no code and no technical design, speaks to no builder and no code host, copies no product per company, records no capability as a product, and names no person. Rates are versioned data, never a code release (items 6 to 11).

Where this blueprint stands. No instance has run. The part card is DRAFT, with last_result NOT_RUN (Protocol §18, item 12). The product line to the engineering AIOC has no Library contract yet; Annex A gives its field lists, and a contract is drafted upstream (upstream/PROPOSALS.md, item 1). The decisions only a human seat can take are listed once, in §13.

Reading (49GAION DR-0041). The complete definition of 49GAION, approved by its governing seat on 25 October 2026, is 49GAION-FRAMEWORK.md in github.com/49g-holding/49GAION. Where this repository differs from it, the definition governs, and this text is read with it. Every rule here that names [ORG]AIOC-OCO or the human hub reads as the Top Management Group, the hub of the operation, human and AI. The panel is the organisation's own code interface, and the AI chat workspace is its back office. The readings are in decisions/DR-0004. Nothing here is removed.

0. Identity and lineage

Lineage. The part was stated by the governing seat of 49GAION on 15 October 2026 as the organisation's one product division (Protocol §18), from a first organisation's need for one home for the what and the why of every product, apart from engineering. This is its first blueprint. Its mother lives in its own public repository because the first instance's home holds that organisation's products and categories (49GAION/DR-0024).

1. Card (49GAION Operating Protocol §3)

card:
  unit_kind: "AIOC"
  code: "[ORG]AIOC-PC"
  parent: "[ORG]AIOC-CH"                  # example code of the Charter, the root AIOC; only it has parent none (Standard §1.7, item 13)
  inner_units: ["[ORG]CELL-CPO", "[ORG]CELL-COSPC", "[ORG]POD-PCCO", "[ORG]POD-EPT"]
  type: "structural"
  org_aion: "[ORG]AION"
  card_version: "v0.1.3"
  input_door: "Chief of Staff"
  wake: { method: "queue", verified: false }
  receives:
    - kind: "product request"             # product direction and product requests, from the Requesting Authority's Cell and from a position of each company, through the HU input port; references only
      format: "Work Item (ID + version) naming the requesting position, the company or market it is for, and what is asked; sources by reference"
      acceptance_test: "TEST-PC v1, cases 2, 14, 15"
      decision_needed: false
    - kind: "source reference"            # the organisation's sources (product documents, terms, policies, data), from the output socket of [ORG]AIOC-SL
      format: "source reference (ID + version + hash; held or not held)"
      acceptance_test: "TEST-PC v1, cases 16, 22"
      decision_needed: false
    - kind: "product signal"              # performance, customer voice, complaints and support, from products in use, through the tool gateway
      format: "Work Item or record reference (ID + version)"
      acceptance_test: "TEST-PC v1, cases 31, 32"
      decision_needed: false
    - kind: "engineering request"         # a question, a first-look build or an acceptance request from the engineering AIOC, on the product line
      format: "Work Item (ID + version) citing the product package (manifest hash) and the criterion it concerns"
      acceptance_test: "TEST-PC v1, cases 11, 27, 28"
      decision_needed: false
    - kind: "rate record"                 # the read-back of a rate written to the rate and configuration store
      format: "versioned record (ID + version), read back"
      acceptance_test: "TEST-PC v1, case 8"
      decision_needed: false
  delivers:
    - kind: "product package"             # the PRD, feature packages with acceptance criteria, designs for every state and copy in every language, on the product line
      format: "frozen, content-addressed package (manifest + parts by hash; Annex A)"
      usual_receivers: ["<code of the engineering AIOC>"]
    - kind: "answer or acceptance"
      format: "Work Item (ID + version): an answer to a question, a first-look note, or an acceptance criterion by criterion"
      usual_receivers: ["<code of the engineering AIOC>"]
    - kind: "rate record"
      format: "versioned record (ID + version) with its effective date, its reason and the record it replaces (Annex B)"
      usual_receivers: ["the rate and configuration store"]
    - kind: "explainer filing"
      format: "versioned document (explainer, questions and answers, help article, user guide, partner material, internal training), filed into Source Lifecycle as a source"
      usual_receivers: ["[ORG]AIOC-SL"]
    - kind: "product review outcome"
      format: "Work Item (ID + version): keep, fix, grow or retire, with its evidence"
      usual_receivers: ["the Requesting Authority's Cell"]
  anatomy:
    panel: { health: { tests: true, metrics: ["stuck", "returned", "late", "products by stage", "packages refused by the auditor", "questions open from engineering", "acceptances open", "rates changed", "rates reversed", "explainers missing", "reviews held"] } }
    back_office: { converses_with_humans: true, hosts: ["Chief of Staff", "Office"], protocol_traffic: true }
    definition: { location: "<org>aioc-pc, blueprint/PC-BLUEPRINT.md", version: "v0.1.3" }
    delivery: { rollback: "one-click" }
    connectors:
      - { role: "the product line to the engineering AIOC", connector: "<engineering AIOC> product line port", access_managed_in: "panel" }   # the grant is signed at the tool gateway as connect-external-port
      - { role: "source of record", connector: "[ORG]AIOC-SL output socket", access_managed_in: "panel" }
      - { role: "rate and configuration store (versioned)", connector: "<store>", access_managed_in: "panel" }
      - { role: "product signals", connector: "<signal source>", access_managed_in: "panel" }
    gateway: { metering_id: "<per-AIOC metering id>" }
  full_name: "Product Core"
  version: "0.1.3"
  lineage: { id: "[ORG]AIOC-PC", version: "0.1.2", relation: "original" }
  lifecycle_state: "designed"
  blueprint_version: "v0.1.3"
  template_version: "v1.5.0"
  accountable_to: "[ORG]CELL-TMS"         # example code of the Cell carrying [ORG]HOAC-TM (Naming Standard R15); never a Cell inside this AIOC
  top_cell: "[ORG]CELL-CPO"
  hoac: "[ORG]HOAC-ACS"
  label_holder: "[ORG]CELL-CPO"
  fixed_test: { id: "TEST-PC", version: "v1", owner: "[ORG]CELL-TMS" }
  skills:
    - { id: "pc-intake", name: "Product intake: the what and the why, apart from the how and the when", tags: ["product", "intake"] }
    - { id: "pc-portfolio", name: "The portfolio of products and their categories", tags: ["product", "portfolio"] }
    - { id: "pc-prd", name: "PRDs and feature packages with acceptance criteria", tags: ["product", "requirements"] }
    - { id: "pc-design", name: "Product design: flows, every state, copy in every language", tags: ["product", "design"] }
    - { id: "pc-build-partner", name: "Partnership in build: answers, first look, acceptance", tags: ["product", "build"] }
    - { id: "pc-run", name: "The run: rates as data, performance, customer voice", tags: ["product", "run"] }
    - { id: "pc-explainers", name: "Explainers and supporting documents", tags: ["product", "documents"] }
    - { id: "pc-review", name: "The weekly product review; refresh or retire", tags: ["product", "review"] }
  ports:
    - { unit: "[ORG]AIOC-PC", port: "ai-in", direction: "input", type: "AI", identification: "technical-key", accepted_content: ["source reference", "product signal", "engineering request", "rate record"], authority_limit: "read only, within the scopes signed for each connection; requests on the product line only", audit_trail: "unit register; the serve logs of [ORG]AIOC-SL and of the engineering AIOC", required_tests: ["TEST-PC v1"], enforcement: "shared-gateway-outside-unit" }
    - { unit: "[ORG]AIOC-PC", port: "ai-out", direction: "output", type: "AI", identification: "technical-key", accepted_content: ["product package", "answer or acceptance", "rate record", "explainer filing", "product review outcome"], authority_limit: "packages, answers and acceptances on the product line only; rate records signed by the product's owner position; filings of its own documents only; never code, technical design or an instruction to a builder", audit_trail: "Work Item record and the unit register", required_tests: ["TEST-PC v1"], enforcement: "shared-gateway-outside-unit" }
    - { unit: "[ORG]AIOC-PC", port: "hu-in", direction: "input", type: "HU", identification: "live-human-sign-in-at-gateway", accepted_content: ["product request from the Requesting Authority's Cell or a company's position (references only)", "a decision of the Chief Product Officer or of a product owner position", "run control and configuration from the Chief Product Officer (never a source)"], authority_limit: "the signer's authority_scope; nothing received here is a source", audit_trail: "Office record", required_tests: ["TEST-PC v1"], enforcement: "shared-gateway-outside-unit" }
    - { unit: "[ORG]AIOC-PC", port: "hu-out", direction: "output", type: "HU", identification: "live-human-sign-in-at-gateway", accepted_content: ["review brief to the Chief Product Officer", "decision rows to the owner positions", "product review outcome to the Requesting Authority's Cell"], authority_limit: "information and proposals only; never a decision, an instruction or a question about a person", audit_trail: "Office record", required_tests: ["TEST-PC v1"], enforcement: "shared-gateway-outside-unit" }
    - { unit: "[ORG]AIOC-PC", port: "stop", direction: "input", type: "HU", identification: "live-human-sign-in-at-gateway", accepted_content: ["stop"], authority_limit: "stop only", audit_trail: "unit register", required_tests: ["TEST-PC v1"], enforcement: "shared-gateway-outside-unit", stop_door: true }
  configuration:                          # every slot is set by the organisation (§15); an empty slot fails the joining test
    office_accountable_human: { value: "<set by the organisation>", set_by: "<position>", date: "<date>", version: "<vN>" }
    central_head: { value: "<the OCO of this [ORG]AION>", set_by: "<position>", date: "<date>", version: "<vN>" }
    discussion_limits: { value: "<set by the organisation>", set_by: "<position>", date: "<date>", version: "<vN>" }
    waiting_deadlines: { value: "<per status>", set_by: "<Cell carrying [ORG]HOAC-TM>", date: "<date>", version: "<vN>" }
    bounce_limit: { value: "<number>", set_by: "<position>", date: "<date>", version: "<vN>" }
    chain_depth: { value: "<number, at least 1>", set_by: "<position>", date: "<date>", version: "<vN>" }
    halt_request_priority: { value: "immediate", set_by: "<position>", date: "<date>", version: "<vN>" }
    budget_cap: { value: "<amount per period>", set_by: "<Cell carrying [ORG]HOAC-TM>", date: "<date>", version: "<vN>" }
    unattended_action: "read-record-triage"
    requesting_authority_cell: { value: "<set by the organisation>", set_by: "<Cell carrying [ORG]HOAC-GOV>", date: "<date>", version: "<vN>" }
    engineering_aioc: { value: "<code of the organisation's engineering AIOC>", set_by: "<Cell carrying [ORG]HOAC-TM>", date: "<date>", version: "<vN>" }
    categories_record: { value: "<reference to the organisation's own category record; never in the Library>", set_by: "[ORG]CELL-CPO", date: "<date>", version: "<vN>" }
    review_day: { value: "<weekday of the weekly product review>", set_by: "[ORG]CELL-CPO", date: "<date>", version: "<vN>" }
    rate_signers: { value: "<per product: the owner position; and whether a rate change is also commit-money, with its limits (§13, H-03)>", set_by: "<Cell carrying [ORG]HOAC-TM>", date: "<date>", version: "<vN>" }
    audit_families_min: { value: 2, set_by: "<position>", date: "<date>", version: "<vN>" }

Joining the protocol. This AIOC joins only after every input and output on this card passes fixed samples (the joining test, Protocol §11, item 1; Standard §3.2, item 4). It also needs the engineering AIOC to accept product packages only on the product line and to send its questions, first looks and acceptance requests back on it, and Source Lifecycle to accept its documents as sources. Until then its lifecycle_state stays designed and no Work Item is routed to it. The cards of its Pods and Cells are set in §17 and generated into cards/.

2. Organisation table and placement

2.1 Organisation table

The blueprint writes [ORG] for the organisation's prefix, as central texts do (Naming Standard R13); each organisation fills it in its own copy. Positions only; who holds each one is kept only in the private register copy (Standard §5.2, Position Principle; 49GAION/DR-0011).

2.2 Placement

• Where it sits. A top-level AIOC under the Charter, accountable to the Cell carrying [ORG]HOAC-TM, beside the engineering AIOC (Protocol §18, item 1).
• Its role. The organisation's one product division: it owns the what and the why of every product for the product's whole life (item 2).
• Scope: does. Product intake; the portfolio and its categories; research; PRDs and feature packages; design; partnership in build; launch; the run (rates as data, performance and profit and loss, communications and retention, customer voice and complaints, operations and upkeep); explainers and supporting documents; refresh or retire; the shared standards of the part (items 3 to 8).
• Scope: does not. Code, technical design, infrastructure, the build plan or its dates (the engineering AIOC); a contract, a legal filing or a money commitment (Human Floor seats); the organisation's own sources (Source Lifecycle); any instruction to a builder (item 10).
• Companies it serves. Every company the organisation runs, and every market it offers in. A product is made once and configured for each company and market, never copied (item 9).
• Boundaries with other AIOCs.
  • The engineering AIOC holds the how and the when. The only line between the two is the product line: complete product packages go out; questions, first-look builds and acceptance requests come back. A finding in build that would change the product comes back as a question (item 10).
  • Source Lifecycle holds every source. This AIOC reads sources by reference and files its own documents into it as sources; it keeps no second copy (Protocol §13).
  • The design stages (Target Operating Model, Process and Position Design, Delivery and Implementation) design the organisation. Where a decided design places a capability or process in Product Core, this AIOC reads it by reference from Source Lifecycle; it never designs the organisation.
• Overlap. None by design. A product decision found elsewhere is returned to this AIOC; a how or when decision found here is returned to the engineering AIOC (TEST-PC v1, case 2).

3. Positions

Every human position is a HOAC position, a legal persona; no natural person exists in the system (Standard §1.1, item 9; 49GAION/DR-0013, DR-0015). Two positions are two parties. Who holds a position, and how, is the organisation's own mechanism, outside the system, never in this file.

One product, one owner (Protocol §18, item 5). An owner position holds no other product; a product has exactly one owner position. A product with no owner position, or an owner position named for two products, fails (TEST-PC v1, cases 5, 48).

Each position's role pack is carried in the role cards of the capabilities it performs (§4, §5).

4. Standard capabilities

4.1 Office

Definition

Default (49GAION-aioc docs/STANDARD-CAPABILITIES.md §4.1) · form: single Chief of Staff. An Office is proposed to the Chief Product Officer when the queue exceeds the waiting deadlines for two review periods; it is never self-created.

Process (SOP)

Default.

Role card

Default; Performed by: an agent; Reports to: the Chief Product Officer.

Fixed test

TEST-PC v1, case 38 · result NOT_RUN

4.2 Chief of Staff

Definition

Default, with these additions. It is this AIOC's voice to its HOAC seats; input arrives only through the typed ports and the Input socket. It holds the product line: it sends only frozen packages that the Independent Package Auditor has passed, and it routes every question, first-look build and acceptance request from the engineering AIOC to the product's team. It writes no product content of its own.

Process (SOP)

Role card

Fixed test

TEST-PC v1, case 37 (the default Chief of Staff test, (a) to (h)), and cases 1, 2, 11, 14 to 16, 25 to 27, 39, 41, 44, 45 · result NOT_RUN

4.3 Input socket

Definition

Default · this AIOC's standard format: a Work Item (ID + version) with its sources by reference. Converters: product request; source reference; product signal; engineering request; rate record read-back.

Process (SOP)

Default. Each converter checks the shape of its input and refuses with a reason: a product request with no requesting position; a source that does not come from Source Lifecycle's output socket; a signal with no product or no date; an engineering request that cites no package manifest hash; a rate read-back whose hash does not match the record written.

Role card

Default; Performed by: the Chief of Staff.

Fixed test

TEST-PC v1, case 39 (one good and one bad sample per converter) · result NOT_RUN

4.4 Panel

Definition

Default. The Panel shows, per product, its stage, its team, its open questions from engineering, its open acceptances, its rates and their history, and its explainers; and, for the CPO Office, the portfolio and the review outcomes.

Process (SOP)

Default.

Role card

Default.

Fixed test

TEST-PC v1, case 40 (the default Panel test) · result NOT_RUN

5. Functional capabilities

5.0 The stages: input, output, done-test

The work of each product runs in the eight stages of Protocol §18, item 6, in order, carried by the product's one team. The CPO Office's capabilities (5.1, 5.2, 5.10, 5.11) run beside them. A product moves to the next stage only when the stage's done-test passes and its owner position decides the move; a skipped stage fails (TEST-PC v1, case 20).

A product goes back from P4 to P2 or P3 only as a new package version, when a question from the engineering AIOC is answered by a change to the product (Protocol §18, item 10).

5.1 Product Intake

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 2, 14, 15 · result NOT_RUN

5.2 Portfolio and Categories

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 4, 5, 10, 17, 18 · result NOT_RUN

5.3 Research and Opportunity

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 19, 20 · result NOT_RUN

5.4 PRD and Feature Packages

Definition

Process (SOP)

Role card

The Independent Package Auditor ([ORG]CELL-IPA, in the CPO Office Pod) is bound to an engine of a different family from the writer's where the engine register allows (slot audit_families_min); an audit run on the writer's own engine binding stops the package (TEST-PC v1, case 21).

Fixed test

TEST-PC v1, cases 7, 21, 22 · result NOT_RUN

5.5 Design

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 23, 24 · result NOT_RUN

5.6 Partnership in Build

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 11, 25 to 28 · result NOT_RUN

5.7 Launch

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, case 29 · result NOT_RUN

5.8 Run

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 8, 30 to 32 · result NOT_RUN

5.9 Explainers and Supporting Documents

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 13, 33 · result NOT_RUN

5.10 Product Review, Refresh or Retire

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 34, 35 · result NOT_RUN

5.11 Shared Standards

Definition

Process (SOP)

Role card

Fixed test

TEST-PC v1, cases 9, 24, 36 · result NOT_RUN

6. Coordination and routes

• Whom it works with. The engineering AIOC, on the product line only; Source Lifecycle, through its output socket and its intake; the Requesting Authority's Cell and each company's positions, through the HU ports; the organisation's signal sources and its rate and configuration store, through the tool gateway. Always through the 49GAION Operating Protocol: one Work Item per hand-off, this AIOC's Chief of Staff as its door.
• Routing rows this AIOC contributes. A product request → [ORG]AIOC-PC. A how or when matter found here → the engineering AIOC. A product finding found in build → back to [ORG]AIOC-PC as a question. A product document → [ORG]AIOC-SL as a source.
• Requests and objections. Owners do not design or change this AIOC's AIs: every proposal, correction or critique is a design-proposal Work Item to OCO; where they disagree, the Chief Product Officer may hold the objection open until it reaches the HOAC seat accountable for OCO, which decides.

7. Records and where things live

8. Tools and the shared AI gateway

All model calls go through the tool gateway of the [ORG]AION. Each tool is reached through a swappable connector, recorded by role; access is granted and withdrawn in the Panel. This AIOC's AI usage is metered separately; its budget cap is set in §15.

Mechanism register. A row is never deleted.

Reserve.

9. Fixed tests: index, triggers and scores

• Re-run triggers: any change to a model, instructions, this AIOC's card, this blueprint, Protocol §18, a shared standard, a tool or its access, or the product line's contract.
• The Library's cases. TEST-PC v1 keeps the Library's TEST-PRODUCT-CORE v1, cases 1 to 13, unchanged, as its own cases 1 to 13 (tests/TEST-PC.md). No case is weakened.
• Complete only when every capability's test has a visible result. NOT_RUN is never PASS.

Checks that are not fixed tests.

• Discriminating evidence. A passing check counts only if it has been shown able to fail on the case it guards; evidence is written by the runner, never by the worker.

10. Build: what is generated from this file

Delivery path: definition change → tests → Panel and Back office update → one-click rollback to the previous commit.

11. Exceptions

• Office. A single Chief of Staff; an Office only when proposed and approved (§4.1).
• Product teams are made from a pattern. §17 sets one product team, named Example, as the pattern. An instance makes one team per product from it, named by the product, each a Pod created under create-or-install-unit and checked against its register before first use (Naming Standard §5, R15). The pattern itself is never created as a team.
• No code project. Product Core writes no code (Protocol §18, item 6.4).

12. Lessons and proposals to the mother

One dated line per lesson, each written without an organisation's details. Nothing is proposed upstream without the word of the governing seat of 49GAION; the drafts are in upstream/PROPOSALS.md.

1. 2026-10-16 · The product line has no Library contract; every organisation would invent its own package shape. Annex A gives the field lists; a contract is drafted (upstream/PROPOSALS.md, item 1). Test case 25 checks the freeze.

13. For the [ORG]HOAC-ACS seat, and every decision only a human seat can take

14. Change log

15. Configuration

Every slot is filled by the organisation; an AIOC with any empty slot does not pass the joining test (Protocol §11). Each value records who set it, when, and in which version.

16. Type

• Type: Structural, as in §0.
• Why this AIOC exists in this organisation: <organisation> has one product division, shared by every company it runs, so that every product has one home for its what and its why.
• Type-specific test: TEST-PC v1, cases 1 to 13 · result NOT_RUN.

17. Cells and Pods

The parts inside this AIOC (docs/CELLS-AND-PODS.md of 49GAION-aioc). The role and nature of this AIOC are read from the type of its top Cell, the Chief Product Officer. Every field that points to a human takes a position code only.

The product team pattern (Protocol §18, item 5). [ORG]POD-EPT and its Cells are the pattern for one product's team, named here for a product called Example. An instance makes one Pod per product from it: the product's name replaces Example in every full name, and every code is the initials of its full name (Naming Standard R15), checked against the organisation's register before first use (§5). One owner position, human, with its HOAC label; six AI members by function: product management and the PRD, design, analysis, pricing and product economics, operations and customer voice, documentation. The team stays with its product for every stage.

The card data (the blueprint governs). tools/make_cards.py expands the block below into the complete unit cards and bot identity cards, writes them into cards/, and checks them against the schemas of 49GAION-protocol, Naming Standard R15 and R16, and this blueprint.

parts:
  defaults:
    accountable_to: "[ORG]CELL-CPO"
    card_version: "v0.1.3"
    version: "0.1.3"
    lifecycle_state: "designed"
    test_version: "v1"
    test_owner: "[ORG]CELL-CPO"
    accountable_human: "[ORG]HOAC-ACS (the Chief Product Officer, [ORG]CELL-CPO)"
    audit_trail: "the run record of [ORG]AIOC-PC"
    hu_in: ["run control and configuration from the Chief Product Officer (never a source)"]
    hu_out: ["report to the Chief Product Officer"]
  cells:
    - code: "[ORG]CELL-CPO"
      full_name: "Chief Product Officer"
      parent: "[ORG]AIOC-PC"
      type: "Human Seat"
      filler_kind: "human"
      hoac: "[ORG]HOAC-ACS"
      accountable_to: "[ORG]CELL-TMS"       # example code of the Cell carrying [ORG]HOAC-TM
      entity: "<entity>"
      authority_scope:
        decision_types: ["create-or-install-unit", "retire-unit", "change-filler", "delegate-authority", "change-fixed-test-or-threshold", "restart-stopped-unit"]
        entity: "<entity>"
        expires: "2027-10-15"                # placeholder; each organisation sets it
        authority: "delegated"
      test: { id: "TEST-PC-CPO", cases: "3, 18, 34, 35, 42, 43", owner: "[ORG]CELL-TMS" }
      ai_in: ["review brief", "product proposals", "decision rows"]
      ai_out: ["run control and configuration"]
      hu_in: ["direction from the Cell carrying [ORG]HOAC-TM", "product direction from the Requesting Authority's Cell"]
      hu_out: ["decisions under live sign-in", "report to the Cell carrying [ORG]HOAC-TM"]
    - code: "[ORG]CELL-COSPC"
      code_rule: "R16"                     # 49GAION/DR-0028; replaces [ORG]CELL-PCCS (retired, R5)
      lineage: { id: "[ORG]CELL-PCCS", version: "0.1.0", relation: "derived" }
      full_name: "Product Core Chief of Staff"
      role: "Chief of Staff"
      parent: "[ORG]AIOC-PC"
      type: "AI Chief of Staff"
      filler_kind: "ai"
      cell_kind: "chief-of-staff-cell"
      test: { id: "TEST-PC-COSPC", cases: "1, 2, 11, 14-16, 25-27, 37, 39, 41, 44, 45" }
      ai_in: ["source reference", "product signal", "engineering request", "rate record read-back", "drafts and records of the Pods"]
      ai_out: ["dispatch to a Pod", "audit request", "product package", "answer or acceptance", "rate record", "explainer filing", "product review outcome"]
      hu_in: ["product request (references only)", "a decision of the Chief Product Officer or of an owner position", "run control from the Chief Product Officer"]
      hu_out: ["review brief to the Chief Product Officer", "decision rows to the owner positions", "product review outcome to the Requesting Authority's Cell"]
      external_ports:
        - { port: "eng-out", direction: "output", accepted_content: ["product package", "answer or acceptance", "launch decision"], authority_limit: "the product line only, under the scope signed under connect-external-port over the engineering AIOC; frozen, audited and decided packages only", audit_trail: "unit register; the Work Item record" }
        - { port: "eng-in", direction: "input", accepted_content: ["question", "first-look build", "acceptance request"], authority_limit: "requests that cite a sent package by manifest hash, on the product line only", audit_trail: "unit register; the Work Item record" }
        - { port: "sl-in", direction: "input", accepted_content: ["source reference"], authority_limit: "the read scope signed under connect-external-port over [ORG]AIOC-SL", audit_trail: "unit register; serve log of [ORG]AIOC-SL" }
        - { port: "sl-out", direction: "output", accepted_content: ["explainer filing", "needs request"], authority_limit: "this AIOC's own documents, with the owner position as contributor", audit_trail: "unit register; serve log of [ORG]AIOC-SL" }
        - { port: "rates-out", direction: "output", accepted_content: ["rate record"], authority_limit: "a rate record decided by the product's owner position under live sign-in", audit_trail: "unit register; the store's version log" }
        - { port: "rates-in", direction: "input", accepted_content: ["rate record read-back"], authority_limit: "read only", audit_trail: "unit register; the store's version log" }
        - { port: "signals-in", direction: "input", accepted_content: ["product signal"], authority_limit: "read only, within the scope signed for the signal source", audit_trail: "unit register" }
      bot:
        allowed_actions: ["record and route every input", "dispatch Cells of this AIOC", "send a package for audit", "freeze a decided package and send it on the product line", "route engineering requests and chase answers", "write a decided rate record and read it back", "file an approved document into Source Lifecycle", "prepare the review brief"]
        ask_first_actions: ["a budget above the cap", "any change to configuration", "anything outside its role card"]
    - { code: "[ORG]CELL-PIC", full_name: "Product Intake Clerk", role: "Product Intake Clerk", parent: "[ORG]POD-PCCO", type: "AI Agent", filler_kind: "ai", test: { id: "TEST-PC-PIC", cases: "2, 14, 15" }, ai_in: ["product request"], ai_out: ["intake record", "classification"], bot: { allowed_actions: ["record and classify product requests"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-PK", full_name: "Portfolio Keeper", role: "Portfolio Keeper", parent: "[ORG]POD-PCCO", type: "AI Agent", filler_kind: "ai", test: { id: "TEST-PC-PK", cases: "4, 5, 10, 17, 18" }, ai_in: ["decisions of the Chief Product Officer", "stage moves"], ai_out: ["register row", "check record", "team proposal"], bot: { allowed_actions: ["write and check portfolio rows", "prepare a team proposal from the pattern"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-SK", full_name: "Standards Keeper", role: "Standards Keeper", parent: "[ORG]POD-PCCO", type: "AI Agent", filler_kind: "ai", test: { id: "TEST-PC-SK", cases: "9, 24, 36" }, ai_in: ["requests from the teams"], ai_out: ["standard draft", "version notice"], bot: { allowed_actions: ["draft changes to the shared standards", "publish a decided version"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-PRS", full_name: "Product Review Secretary", role: "Product Review Secretary", parent: "[ORG]POD-PCCO", type: "AI Agent", filler_kind: "ai", test: { id: "TEST-PC-PRS", cases: "32, 34, 35" }, ai_in: ["product records"], ai_out: ["review brief", "review record"], bot: { allowed_actions: ["prepare the weekly review brief", "record the outcomes decided"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-IPA", full_name: "Independent Package Auditor", role: "Independent Package Auditor", parent: "[ORG]POD-PCCO", type: "AI Agent", filler_kind: "ai", test: { id: "TEST-PC-IPA", cases: "7, 21-23, 25" }, ai_in: ["audit request"], ai_out: ["audit record"], bot: { allowed_actions: ["check a package for completeness, criteria, citations, states, languages and the absence of code"], ask_first_actions: ["anything outside its role card"] } }
    - code: "[ORG]CELL-EPO"
      full_name: "Example Product Owner"
      parent: "[ORG]POD-EPT"
      type: "Human Seat"
      filler_kind: "human"
      hoac: "[ORG]HOAC-ACS"
      accountable_to: "[ORG]CELL-CPO"
      entity: "<entity>"
      authority_scope:
        decision_types: []                   # the product's own decisions are ordinary decisions under live sign-in; commit-money is added only where the organisation sets it (§13, H-03)
        entity: "<entity>"
        expires: "2027-10-15"                # placeholder; each organisation sets it
        authority: "delegated"
      test: { id: "TEST-PC-EPO", cases: "5, 20, 28-30, 48", owner: "[ORG]CELL-CPO" }
      ai_in: ["decision rows of its product"]
      ai_out: ["decisions of its product"]
      hu_in: ["direction from the Chief Product Officer"]
      hu_out: ["decisions, acceptances and rate decisions under live sign-in", "report to the Chief Product Officer"]
    - { code: "[ORG]CELL-EPM", full_name: "Example Product Manager", role: "Product Manager", parent: "[ORG]POD-EPT", type: "AI Agent", filler_kind: "ai", accountable_to: "[ORG]CELL-EPO", accountable_human: "[ORG]HOAC-ACS (the product's owner position, [ORG]CELL-EPO)", test: { id: "TEST-PC-EPM", cases: "7, 19, 20, 22, 26, 29", owner: "[ORG]CELL-EPO" }, ai_in: ["intake record", "research evidence", "engineering request"], ai_out: ["research record", "PRD and feature packages", "answer draft", "launch record draft"], bot: { allowed_actions: ["write the research record, the PRD and feature packages", "draft answers and launch records"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-EPD", full_name: "Example Product Designer", role: "Product Designer", parent: "[ORG]POD-EPT", type: "AI Agent", filler_kind: "ai", accountable_to: "[ORG]CELL-EPO", accountable_human: "[ORG]HOAC-ACS (the product's owner position, [ORG]CELL-EPO)", test: { id: "TEST-PC-EPD", cases: "23, 24, 27", owner: "[ORG]CELL-EPO" }, ai_in: ["decided PRD", "design system"], ai_out: ["flows, screens and copy", "first-look note"], bot: { allowed_actions: ["design flows and screens in every state", "write copy in every language served"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-EPA", full_name: "Example Product Analyst", role: "Product Analyst", parent: "[ORG]POD-EPT", type: "AI Agent", filler_kind: "ai", accountable_to: "[ORG]CELL-EPO", accountable_human: "[ORG]HOAC-ACS (the product's owner position, [ORG]CELL-EPO)", test: { id: "TEST-PC-EPA", cases: "19, 32", owner: "[ORG]CELL-EPO" }, ai_in: ["source references", "product signals"], ai_out: ["evidence list", "performance record"], bot: { allowed_actions: ["gather evidence by reference", "compute performance and profit and loss from source records"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-EPEA", full_name: "Example Pricing and Economics Analyst", role: "Pricing and Economics Analyst", parent: "[ORG]POD-EPT", type: "AI Agent", filler_kind: "ai", accountable_to: "[ORG]CELL-EPO", accountable_human: "[ORG]HOAC-ACS (the product's owner position, [ORG]CELL-EPO)", test: { id: "TEST-PC-EPEA", cases: "8, 30", owner: "[ORG]CELL-EPO" }, ai_in: ["rate request", "pricing models", "terms"], ai_out: ["rate draft", "product economics section"], bot: { allowed_actions: ["draft rate changes as versioned records", "write the product economics section"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-EOCVA", full_name: "Example Operations and Customer Voice Agent", role: "Operations and Customer Voice Agent", parent: "[ORG]POD-EPT", type: "AI Agent", filler_kind: "ai", accountable_to: "[ORG]CELL-EPO", accountable_human: "[ORG]HOAC-ACS (the product's owner position, [ORG]CELL-EPO)", test: { id: "TEST-PC-EOCVA", cases: "31", owner: "[ORG]CELL-EPO" }, ai_in: ["product signal"], ai_out: ["signal record", "complaint route", "upkeep request draft"], bot: { allowed_actions: ["record customer voice, complaints, support and performance readings against the product", "route complaints on the organisation's complaints path"], ask_first_actions: ["anything outside its role card"] } }
    - { code: "[ORG]CELL-EDW", full_name: "Example Documentation Writer", role: "Documentation Writer", parent: "[ORG]POD-EPT", type: "AI Agent", filler_kind: "ai", accountable_to: "[ORG]CELL-EPO", accountable_human: "[ORG]HOAC-ACS (the product's owner position, [ORG]CELL-EPO)", test: { id: "TEST-PC-EDW", cases: "13, 33", owner: "[ORG]CELL-EPO" }, ai_in: ["PRD, design, rates, launch record"], ai_out: ["explainer set drafts"], bot: { allowed_actions: ["write the explainer and supporting documents of the product"], ask_first_actions: ["anything outside its role card"] } }
  pods:
    - { code: "[ORG]POD-PCCO", full_name: "Product Core CPO Office", type: "AI Pod", inner_units: ["[ORG]CELL-PIC", "[ORG]CELL-PK", "[ORG]CELL-SK", "[ORG]CELL-PRS", "[ORG]CELL-IPA"], top_cell: "[ORG]CELL-PK", test: { id: "TEST-PC-PCCO", cases: "4, 9, 14, 15, 17, 21, 34, 36" }, ai_in: ["product request", "audit request", "product records"], ai_out: ["intake record", "register row", "audit record", "review brief", "standard version"] }
    - { code: "[ORG]POD-EPT", full_name: "Example Product Team", type: "Product Team", inner_units: ["[ORG]CELL-EPO", "[ORG]CELL-EPM", "[ORG]CELL-EPD", "[ORG]CELL-EPA", "[ORG]CELL-EPEA", "[ORG]CELL-EOCVA", "[ORG]CELL-EDW"], top_cell: "[ORG]CELL-EPO", hoac: "[ORG]HOAC-ACS", label_holder: "[ORG]CELL-EPO", test: { id: "TEST-PC-EPT", cases: "6, 19, 20, 23, 29-33" }, ai_in: ["dispatch from the Chief of Staff"], ai_out: ["the product's records and packages"] }

• Accountability. The CPO Office Pod, its Cells, the Chief of Staff and each product team are accountable_to [ORG]CELL-CPO. Each team's AI Cells are accountable_to the team's owner position. The AIOC itself and the Chief Product Officer are accountable_to the Cell carrying [ORG]HOAC-TM.
• Bots. Each AI Cell's bot (twelve in the pattern) has its own identity card, its own credential, never_signs: true, and its memory sealed on a change of filler (Protocol §10, item 3). The credential IDs in cards/bots/ are placeholders; the credentials live only in the organisation's vault.
• The Requesting Authority, the positions of each company, the engineering AIOC and Source Lifecycle are not Cells of this AIOC.

Code checks (Naming Standard R15, R16 and §5), recorded on 16 October 2026; the Chief of Staff's COS code on 19 October 2026. Each organisation repeats the check of §5.2 against its own register before first use.

No code of this blueprint uses the suffix PC alone, so no part can be read as the AIOC itself. UNVERIFIED against any organisation's unit register; each organisation checks them in its own.

Annex A. The product package and the records of a product's life

Field lists. Every field is filled; "none" is an answer (Protocol §18, item 6.2). A package sent on the product line is frozen and content-addressed: its ID is the hash of its manifest, and the manifest lists every part by hash (card output 1).

A.1 The package manifest

A.2 The PRD

A.3 A feature package

A.4 The design

A.5 The explainer set

The product explainer and its questions and answers; help articles and user guides; partner materials; internal training. Each is a versioned document, filed into Source Lifecycle with the owner position as contributor.

A.6 The launch record

A.7 The retirement record

Annex B. The rate record

A reversal is a new version whose value is an earlier version's value, with its own reason (Protocol §18, item 7).

Annex C. The portfolio register

Which categories an organisation has, and what each holds, is the organisation's own record and never appears in the Library (Protocol §18, item 4).

Annex D. What this AIOC never does

1. Write code, technical design or infrastructure, or set the build plan or its dates.
2. Speak to a builder or to the code host, or send product work other than on the product line.
3. Send an incomplete package, or one the Independent Package Auditor has not passed.
4. Copy a product for a company instead of configuring it.
5. Record a capability as a product.
6. Give one owner position two products, or a product two owner positions, or hand a stage of a product's life to another team.
7. Change a rate by a code release, or without an effective date and a reason.
8. Invent a figure, a target or a price.
9. Name a person, or read who occupies a position.
10. Let an AI decide, accept or sign.
11. Put an organisation's products, categories or rates into the Library.

[ORG]AIOC-PC mother blueprint v0.1.3 · Powered by 49GAION