docs: seed strategic docs into platform/docs root #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/seed-strategic-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Seeds the 12 strategic docs produced over the 2026-05-09 chat
session into
platform/docs/as the canonical "current" set:At platform/docs/ root (8 files):
operating-thesis.mdstrategy.md— consolidatesstrategy.md+strategy-v1.md; v1fully folded in (numbered customer-journey list, geographic Y1-5
plan, IoT progression detail, three-layer data-model elaboration,
pipeline cost framing, indie-vs-enterprise failure-mode
warning); no version-numbered filename retained.
decisions-log.md— consolidatesdecisions-log.md+decisions-log-v1.md; v1 was a strict subset of v2 (D-001 throughD-030 verbatim identical; v2 extends with D-031 through D-040).
technical-architecture.mdarchitecture-summary.mdpartnership-and-channel-map.mdnext-90-days-execution-plan.mdrecalibration-log.mdAt platform/docs/architecture/components/ (4 files):
shared.md,sahaaya.md,realmetre.md,control-plane.mdWhy
These docs are the source-of-truth strategic + architectural
material for the platform going forward. They were produced over an
extended chat session today; until now they've sat in the operator
working tree untracked. Landing them on
main:upcoming doc-trueup pass — the trueup's
cluster-rules.jsondeclares these exact paths as preserve-as-is so they don't get
re-aggregated.
"aggregate and rewrite, don't use version numbers in names").
How verified
agent/seed-strategic-docsmatches the regex; commit follows Conventional Commits
(
docs: seed strategic docs into platform/docs root); this PRbody has the three required sections.
temp/prompts/aggregate-version-pair.txt— latest asstructural backbone, earlier preserved where it adds substance,
contradictions flagged inline (none found in either pair).
content was dropped that wasn't either preserved verbatim or
integrated phrasings; subagent flagged a few areas
(Section 3 numbered-list step 5 in strategy, Section 5
customer-evolution duplication) as worth a human eyeball
during review.
Refs: B3 (
platform/docs/wip/B3-git-policy.md),temp/prompts/aggregate-version-pair.txt,
temp/rules/cluster-rules.json (preserve_as_is_paths).
Adds the strategic docs produced over the 2026-05-09 chat session as the canonical 'current' set under platform/docs/. They become the preserve-as-is anchors for the upcoming doc-trueup pass. Files added (12): - platform/docs/operating-thesis.md - platform/docs/strategy.md (consolidates strategy.md + strategy-v1.md; v1 fully folded in, no version-numbered filename retained) - platform/docs/decisions-log.md (consolidates decisions-log.md + decisions-log-v1.md; v1 was a strict subset of v2) - platform/docs/technical-architecture.md - platform/docs/architecture-summary.md - platform/docs/partnership-and-channel-map.md - platform/docs/next-90-days-execution-plan.md - platform/docs/recalibration-log.md - platform/docs/architecture/components/{shared,sahaaya,realmetre,control-plane}.md The version-pair consolidations follow the rules in temp/prompts/aggregate-version-pair.txt (latest as structural backbone; older preserved where it elaborates; contradictions flagged inline, none found here).