stack

692 Commits 77 Branches 17 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
mos-dt-0andClaude Opus 5	f13222b76b	docs(remediation): charter reflects DECISION-1 corrected wire-in target and current status The charter's build-1 cell still named mosaic_orchestrator.py::run_single_task after DECISION-1 ruled against it. Leaving the charter contradicting the ruled decision would mislead any future reader who starts there — corrected in place with the rationale and provenance, rather than only in TASKS.md. Also: status PLANNING -> EXECUTING; scout TODO discharged (file is in-tree) with a note that its findings stand but its recommended wire-in point is superseded. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 18:07:16 -05:00
mos-dt-0andClaude Opus 5	d1e7ba19ca	docs(remediation): promote observe-the-property principle to charter; bank D-13 dual credential registries Charter gains a first-class principle per Mos: no write is done until the requested PROPERTY is observed; a success exit code is not evidence. Success output is designed to be believed — that is why the inert-gate class exists and why the P-WRAPPER tri-state is not optional. Recorded with its provenance: the orchestrator committed this exact error (D-12), and three of the session's twelve instances were its own. D-13: diagnosing D-12 found two parallel credential registries that can disagree. gitea-mosaicstack-mos-dt-0.token EXISTS, but tea has no mosaicstack login for that identity — so raw-API paths work while tea-dependent wrapper paths silently degrade. tea is not stale; the login does not exist. Capability declared authoritative by the token-file set does not govern the tea path. RM-04 must reconcile the registries (or assert agreement at startup, with a must-fail control). RM-50's pre-dispatch check must verify capability for the path actually used. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 18:06:18 -05:00
mos-dt-0andMos	01e966f36d	docs(remediation): mission charter + reconciled execution backlog (#1026 ) ci/woodpecker/push/publish Pipeline was successful Details ci/woodpecker/push/ci Pipeline was successful Details Co-authored-by: mos-dt-0 <[email protected]>	2026-07-31 22:47:03 +00:00

Author

SHA1

Message

Date

mos-dt-0andClaude Opus 5

f13222b76b

docs(remediation): charter reflects DECISION-1 corrected wire-in target and current status

The charter's build-1 cell still named mosaic_orchestrator.py::run_single_task after
DECISION-1 ruled against it. Leaving the charter contradicting the ruled decision would
mislead any future reader who starts there — corrected in place with the rationale and
provenance, rather than only in TASKS.md.

Also: status PLANNING -> EXECUTING; scout TODO discharged (file is in-tree) with a note
that its findings stand but its recommended wire-in point is superseded.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

2026-07-31 18:07:16 -05:00

mos-dt-0andClaude Opus 5

d1e7ba19ca

docs(remediation): promote observe-the-property principle to charter; bank D-13 dual credential registries

Charter gains a first-class principle per Mos: no write is done until the requested
PROPERTY is observed; a success exit code is not evidence. Success output is designed
to be believed — that is why the inert-gate class exists and why the P-WRAPPER
tri-state is not optional. Recorded with its provenance: the orchestrator committed
this exact error (D-12), and three of the session's twelve instances were its own.

D-13: diagnosing D-12 found two parallel credential registries that can disagree.
gitea-mosaicstack-mos-dt-0.token EXISTS, but tea has no mosaicstack login for that
identity — so raw-API paths work while tea-dependent wrapper paths silently degrade.
tea is not stale; the login does not exist. Capability declared authoritative by the
token-file set does not govern the tea path.

RM-04 must reconcile the registries (or assert agreement at startup, with a must-fail
control). RM-50's pre-dispatch check must verify capability for the path actually used.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

2026-07-31 18:06:18 -05:00

mos-dt-0andMos

01e966f36d

docs(remediation): mission charter + reconciled execution backlog (#1026 )

ci/woodpecker/push/publish Pipeline was successful

Details

ci/woodpecker/push/ci Pipeline was successful

Details

Co-authored-by: mos-dt-0 <[email protected]>

2026-07-31 22:47:03 +00:00