feat(navigability): ADR-0015 navigability-first pivot + MAP.md + docs/domains/ + docs/onboarding/ #182
No reviewers
Labels
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform!182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/navigability-first-MOC-and-MAP"
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
Per operator voice-note 2026-05-11 ~08:10 + GPT-5.5 Pro oracle review Sidebar blind-spot: navigability-first pivot. Pauses Phase 07/08+ capability expansion; ships navigability primitives so operator AND agents can orient themselves in the 81-module platform without re-deriving structure each time.
Operator: "Wydaje mi się, że to ma dać więcej wartości — organizacja i zarząd. Logistyka i zarządzanie. Na tym musimy się w pierwszej kolejności skupić."
GPT: "The platform is no longer capability-constrained. It is interruption-constrained."
Files (6 in repo + 1 in operator's vault)
decisions/0015-navigability-first.mdMAP.mddocs/domains/README.mddocs/onboarding/claude-fresh-session.mddocs/onboarding/codex-fresh-session.mddocs/onboarding/new-agent.md/Users/pd/Iskra-i-Piotr/00 Inbox/MOC-Iskra-Platform.mdTotal in-repo: 6 files, ~1600 LoC.
The pivot (per ADR-0015)
module.yaml, no new capability ADRs (0016+), no new Phase 07/08 follow-ups until navigability primitives land.MAP.mdand relevantdocs/domains/<domain>.md; canary 3+3 checks the field.What this PR DOES
MAP.md— first-read orientation for any fresh agentWhat this PR DOES NOT do
module.yamlor runtime pathINDEX.md(INDEX = module catalog; MAP.md = system orientation)docs/domains/<domain>.mdfiles (follow-up PRs; operator paces)Why this matters NOW
Per operator self-report 2026-05-11 ~08:10:
Per GPT verdict 2026-05-11 Sidebar (predicted this exact moment):
This PR is the operationalization of that verdict.
Acceptance criteria
MAP.mdexists at repo root with mermaid + textual reference + §Quick reference + §FAQdocs/domains/README.mdexists with 7-domain tablels)risk/process(touchesdecisions/extensively + new doc namespaces)AcceptedRollback
Pure additive (6 new files in repo, 0 modified). Reverting deletes the navigability layer (returns operator to pre-pivot state). Safe.
Follow-up PRs (operator-paced after this merges)
docs/domains/<domain>.md— per-domain detail (one per cohort; suggested 1 per day)AGENTS.mdStep-1 amendment — "read MAP.md first" added to fresh-agent protocol (~10 min PR)platformctl validateextension — checks new ADRs have navigability-cost acceptance item (~30 min PR)Refs
Codex effort needed
Review + merge. No runtime change. Acceptance is doc-reviewable + operator-perceived-orientation-improvement. After merge: future PRs gated by navigability-cost rule.
Role: orchestrator / drafter (claude)
Lane: navigability pivot
Next: operator merges → 7 follow-up per-domain PRs at operator's pace → resume Phase 07 implementation work only AFTER Phase 06 prune + navigability layer stable.
Fork A triage (codex): closing as superseded/rewrite-needed.
Navigability remains important, but this PR predates
state/roadmap/current-platform-roadmap.md,state/ANY-COUSIN-WAKEUP.md, ADR-0021 bounded contexts, and the recentINDEX.mddeprecation. It also uses older ADR references and declares a rootMAP.mdas first-read in a way that now conflicts with the current onboarding/roadmap structure.Recommendation: if we still want repo maps, rewrite as an ADR-0021 context-map implementation PR, not as this old ADR-0015 package.
Pull request closed