docs(architecture): add platform foundation v0 #3

Merged

pappi merged 1 commit from agent/add-platform-foundation into main

2026-05-09 16:12:25 +00:00

pappi commented

2026-05-09 04:47:42 +00:00

Owner

What

Adds platform/docs/architecture/foundation/ containing
platform-foundation.md (the architectural foundation), README.md
(folder explanation and version conventions), and CHANGELOG.md
(v0 initial entry).

This is the reference document for every future capability, strategy,
policy, and workflow in the platform. It defines the vocabulary,
operating principles, substrate choices, entity lifecycle, registry
shape, population guidelines, and Code prompt templates that
downstream platform work conforms to.

Why

The platform requires a coherent vocabulary, substrate model, and
lifecycle definition before capability registry population begins.
Without an explicit foundation, capabilities accumulate as
inconsistent fragments, decisions get re-litigated, and every new
piece pays the cost of choosing infrastructure from scratch.

v0 establishes the foundation. Future work — cp-sonar migration to
AWS, PEX redesign through the pipeline, marketing portal dogfood,
any vertical onboarding — references this document for design
decisions and conformance.

How verified

Foundation content authored and reviewed across an extended chat
session on 2026-05-09 (Pappi + Claude chat), with multiple
iterations on taxonomy, OPA commitment, two-bucket substrate
design, lifecycle and locations, and Code prompt templates.
Internal cross-references between sections verified during
assembly (sections 1-10 reference each other consistently).
Conforms to B3 git policy: branch name matches regex, commits use
conventional commits format, PR body has all three required
sections.
registry-check tooling is not yet built; the foundation doc
itself defines what registry-check will validate when built.
This is captured in §10 (Open Items) of the foundation doc.

Note: branch was force-pushed once to swap the prior v0 draft (1299
lines, 9 sections) for this ratified v0 (1448 lines, 10 sections —
adds §6 Lifecycle and Locations). Force-push is policy-allowed on
feature branches per B3 D26.

Refs: A1 (workspace structure), B3 (git policy this PR exercises for
the first time on real content after rollout).

## What Adds `platform/docs/architecture/foundation/` containing `platform-foundation.md` (the architectural foundation), `README.md` (folder explanation and version conventions), and `CHANGELOG.md` (v0 initial entry). This is the reference document for every future capability, strategy, policy, and workflow in the platform. It defines the vocabulary, operating principles, substrate choices, entity lifecycle, registry shape, population guidelines, and Code prompt templates that downstream platform work conforms to. ## Why The platform requires a coherent vocabulary, substrate model, and lifecycle definition before capability registry population begins. Without an explicit foundation, capabilities accumulate as inconsistent fragments, decisions get re-litigated, and every new piece pays the cost of choosing infrastructure from scratch. v0 establishes the foundation. Future work — cp-sonar migration to AWS, PEX redesign through the pipeline, marketing portal dogfood, any vertical onboarding — references this document for design decisions and conformance. ## How verified - Foundation content authored and reviewed across an extended chat session on 2026-05-09 (Pappi + Claude chat), with multiple iterations on taxonomy, OPA commitment, two-bucket substrate design, lifecycle and locations, and Code prompt templates. - Internal cross-references between sections verified during assembly (sections 1-10 reference each other consistently). - Conforms to B3 git policy: branch name matches regex, commits use conventional commits format, PR body has all three required sections. - `registry-check` tooling is not yet built; the foundation doc itself defines what `registry-check` will validate when built. This is captured in §10 (Open Items) of the foundation doc. --- Note: branch was force-pushed once to swap the prior v0 draft (1299 lines, 9 sections) for this ratified v0 (1448 lines, 10 sections — adds §6 Lifecycle and Locations). Force-push is policy-allowed on feature branches per B3 D26. Refs: A1 (workspace structure), B3 (git policy this PR exercises for the first time on real content after rollout).

pappi added 1 commit

2026-05-09 04:47:42 +00:00