docs: align INTENT with work-record framework; propose ISSUE-WP-0005
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s

Rewrite INTENT for UUIDv7+canonical identity, file-first topology, dual
lifecycles, intake+promotion findings path, and shipped vs target connector
surface. Add ISSUE-WP-0005 to implement mapping/store/CLI and close SCOPE
gaps; mark alignment-review remediation done.
This commit is contained in:
tegwick 2026-07-22 00:03:40 +02:00
parent e804c4e15f
commit 058b1b96f6
4 changed files with 438 additions and 134 deletions

View file

@ -322,8 +322,17 @@ honesty without becoming a second inventory.
- connector responsibilities already delivered,
- or “stop IssueSink” without a named intake/promotion destination.
**Suggested next step:** apply the P1/P2 INTENT edits in a small docs PR (or
follow-up session); keep this report as the audit trail.
**Suggested next step (superseded):** apply the P1/P2 INTENT edits…
### Remediation (2026-07-22)
| Item | Status |
| --- | --- |
| P1P3 INTENT edits (shipped vs target, diagram, dual lifecycle, UUIDv7 + canonical id, intake+promotion, unmapped outside spine, kind registry, claim/execute wording) | **Done**`INTENT.md` rewritten 2026-07-22 |
| Implementation of mapping / scope gaps | **Tracked**`workplans/ISSUE-WP-0005-connector-alignment-implementation.md` |
This report remains the audit trail; treat INTENT as current intent, not the
pre-remediation text analyzed above.
---