​
Architecture Artefact Register

This register records where architecture knowledge lives in the workspace and how each artefact family should be treated. Use it when you need to know whether a file is a primary canonical source, a controlled overlay, a standalone governed stream, supporting detail, or reference and prototype history.

​
Register Status

  • Last reviewed: 2026-04-17
  • Governance model: whole-workspace
  • Workspace root: repository root
  • Primary platform root: local-pc/
  • Externalized sibling repos: ghost-os/ is outside the controlled workspace baseline
  • Controlled baseline: Master Document Control

​
Authority Classes

  • Primary canonical: primary source of truth for the main platform architecture baseline.
  • Canonical within contract scope: source of truth for a bounded contract family, schema, or package.
  • Controlled overlay: live tenant or operating view that depends on, but does not replace, the primary canonical platform docs.
  • Canonical stream: a first-class architecture stream with its own current-state source of truth in the workspace.
  • Supporting: important companion detail that enriches canonical docs without outranking them.
  • Supporting or time-bound: useful planning, audit, or rollout material with active but non-permanent authority.
  • Reference: useful context, analysis, or history that should not be treated as current authority.
  • Prototype or archive: exploratory or superseded material retained for history only.

​
Master Register

IDFamilyAuthorityPrimary entrypointScope
AR-001Platform canonical architecturePrimary canonicalArchitecturePaperclip control-plane architecture, system boundaries, and end-to-end data flows
AR-002Tremor operating corpusControlled overlayArchitecture & SchemaTremor company-specific operating, governance, and live wiki layer
AR-003Deep specs and implementation docsSupporting or referencelocal-pc/doc/architecture/Rich detail for warehouse, memory, and implementation architecture
AR-004Plans, contracts, audits, and release governanceSupporting or time-boundlocal-pc/doc/plans/Execution sequencing, audit notes, rollout contracts, and release governance
AR-005Schema and contract packagesCanonical within contract scopemom/contracts/Wire contracts, intake schemas, and portable data-shape definitions
AR-006Tremor native runtime and prototype network docsCanonical streamtremor-native/docs/runtime-architecture.mdNative host/client runtime plus prototype transport history
AR-007Root-level meta and research notesReferencefindings.mdSession notes, working analysis, research, and scratch governance context

​
Register Detail

​
AR-001 Platform canonical architecture

Use this family first when you need the current Paperclip architecture baseline. Primary entrypoints: Notes:
  • This family is the primary canonical platform spine.
  • Changes here should be reflected in the controlled baseline before downstream overlays are updated.
  • packages/db/ remains the runtime source of truth for DB behavior; this docs family is the controlled descriptive surface for operators.

​
AR-002 Tremor operating corpus

Use this family when you need the live Tremor operating and tenant-specific view rather than the stable platform baseline. Primary entrypoints:
  • Architecture & Schema
  • local-pc/docs/operating/
  • local-pc/docs/companies/tremor/wiki/
  • local-pc/docs/companies/tremor/artifacts/
  • local-pc/docs/companies/tremor/agents/, projects/, skills/, and tasks/
Notes:
  • This family is a living overlay on top of the platform architecture.
  • It should not override the canonical contract order recorded in ADR-0003.

​
AR-003 Deep specs and implementation docs

Use this family when canonical docs are too compressed and you need older or deeper detail. Primary entrypoints:
  • local-pc/doc/DATABASE.md
  • local-pc/doc/architecture/DB-INFRA-OVERVIEW.md
  • local-pc/doc/architecture/AGENT-MEMORY-QUALITY-ARCHITECTURE.md
  • local-pc/doc/architecture/INTELLIGENCE-STACK-SCHEMA.md
  • local-pc/doc/implementation/MEMORY-IMPLEMENTATION-SPEC.md
  • local-pc/doc/spec/
  • local-pc/docs/specs/
  • local-pc/docs/specs-and-plans/overview.md
Notes:
  • This family may contain unique detail that has not yet been promoted into canonical docs.
  • local-pc/doc/DATABASE.md is the repo-local DB operations brief that points directly at packages/db runtime entrypoints.
  • Treat it as supporting unless a document is explicitly promoted through the control rules.

​
AR-004 Plans, contracts, audits, and release governance

Use this family for sequencing, implementation governance, and audit history. Primary entrypoints:
  • local-pc/doc/plans/
  • local-pc/doc/treaaa-*-execution-contract.md
  • local-pc/doc/DB-STATE-AUDIT*.md
  • local-pc/doc/treaaa-25-runtime-benchmark-plan.md
  • local-pc/doc/RELEASE-AUTOMATION-SETUP.md
  • local-pc/doc/epoch-*.md
  • local-pc/doc/provenance-*.md
Notes:
  • These artefacts influence delivery and audit posture.
  • They are not stable architecture authority unless explicitly incorporated into canonical docs or ADRs.

​
AR-005 Schema and contract packages

Use this family when the question is about transport shape, intake shape, or portable schema truth. Primary entrypoints:
  • mom/contracts/README.md
  • mom/contracts/*.schema.json
  • paperclip-intake-v1/README.md
  • paperclip-intake-v1/contracts/*.schema.json
  • local-pc/packages/plugins/company-intake/src/pipeline/contracts/*.schema.json
Notes:
  • These artefacts can be canonical within their bounded contract family even when they are not part of the docs site.
  • Contract changes should follow the authority order recorded in ADR-0003.

​
AR-006 Tremor native runtime and prototype network docs

Use this family for the native host/client architecture and transport behavior. Primary entrypoints:
  • tremor-native/docs/runtime-architecture.md
  • tremor-native/docs/low_latency_networking_update.md
Reference or prototype material in the same family:
  • tremor-native/network_architecture.md
  • tremor-native/implementation_plan.md
  • tremor-native/packet_failover_logic.md
  • tremor-native/router_configuration_guide.md
  • tremor-native/mesh_network_prototype/
  • tremor-native/new_mesh_network_prototype/
Notes:
  • runtime-architecture.md is the canonical source for the current native runtime stream.
  • The older mesh, router, and failover notes remain prototype or reference material until updated to match code.

​
AR-007 Root-level meta and research notes

Use this family for reconstruction, context recovery, and background analysis only. Primary entrypoints:
  • findings.md
  • progress.md
  • task_plan.md
  • codex.md
  • gemini.md
  • paperclip-insights.md
  • networking_insights_summary.md
  • frontier-meta-control-methods.md
  • layer3_switch_configurations.md
Notes:
  • These artefacts may explain why decisions were made, but they are not controlled architecture sources.
  • Do not cite them as the final authority when a canonical doc or ADR exists.

​
Promotion Rule

An artefact should only be promoted into a stronger authority class when all of the following are true:
  • it is grounded in the current repository reality rather than speculative target state
  • it has a clear bounded purpose that does not duplicate an existing canonical page
  • it is linked from the controlled docs set or a governing ADR
  • the Master Document Control and this register are updated to reflect the change