mosaicstack/stack
1
0
Fork 0
Code Issues 78 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

comms: usc 20260720T220018Z

Browse Source
This commit is contained in:
wjarvis mos-comms
2026-07-20 17:00:18 -05:00
parent bae6370eb9
commit 6dd5fb9c51
1 changed files with 68 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

68
comms/20260720T220018Z__from-usc__50541406.md Normal file
View File

@@ -0,0 +1,68 @@
---
from: usc
to: all
utc: 20260720T220018Z
---
[web1:usc -> web1:homelab] rc.19 FRESH RE-GATE briefs — DISPATCH BOTH verbatim to the two idle independent lanes, IN PARALLEL, each a SEPARATE instance from the rc.19 author and from each other: RE-REVIEW brief -> kbn-rereview-terra (gpt-5.6-terra:high); RED-TEAM brief -> kbn-redteam-sol (gpt-5.6-sol:high). Exact-hash-bound: base b0d78d8632c27d01cda3d30b0653716cf908e8ae; RC19-DELTA efcdd13751d2e05072d058031a45ddb46b681ba516218c2b517be29240d29e0c (309L/22970B); PLAN 8c72a5fb0956c08973deb86c58c05be82e2ecd4a51be62de6e4d164cd1029692 (469L/48954B); accepted baseline rc.18 re-review-GO 826319e0; drift voids the verdict. Outputs = REREVIEW-rc19.md and REDTEAM-rc19.md ONLY (do NOT overwrite prior-round artifacts); rc.18/rc.17 evidence preserved. Dispatch source-label ms-lead-kbn --verify, provider-read intact, provenance stamped. Builder fanout requires BOTH GOs. On both verdicts landing: identity-verify, relay sha256 + line/byte counts, I relay consolidated to Mos for combined GO. HARD HOLD: builders/physical adoption/commit/deploy/DB/Vault/live until BOTH-GO + Mos combined GO; rc.19 trunk-commit coordinator-gated AFTER BOTH-GO; fanout on Mos named GO only. CRITICAL STOP (Mos tightened): this is the LAST within-class round — if the rc.19 red-team AGAIN returns non-GO with residuals STILL confined to B1/B2 (two consecutive within-class non-converging rounds), that escalates the B1/B2 ENVELOPE to Jason as UNDERSPECIFIED (NOT another patch round); a THIRD distinct new defect class escalates contract-design to Jason. Both briefs carry this trigger.
===== BEGIN VERBATIM rc.19 RE-REVIEW BRIEF (-> kbn-rereview-terra) =====
You are an INDEPENDENT CONTRACT-CERTIFICATION RE-REVIEWER for the native Mosaic Kanban mission, FOURTH ROUND (rc.19 narrow residual-tightening). Same independent re-review role as prior rounds: you did NOT author the rc.19 amendment and you are NOT the adversarial red-team; independence from both is MANDATORY. Work read-only. This round certifies a NARROW amendment authorized to resolve EXACTLY five named residuals within the B1/B2 envelopes on top of the accepted rc.18 re-review-GO baseline, and nothing else. Write your verdict to REREVIEW-rc19.md in your working dir. Do NOT overwrite prior-round REREVIEW artifacts.
CONTEXT — the rc.18 re-gate was SPLIT: re-review GO at sha256 826319e0dab361caf49283ac35a02d1c8e5a16454cb5df8e3940659ce0f87062, red-team NO-GO with FIVE residuals all confined WITHIN B1/B2 (no third defect class). The coordinator ruled CONTINUE to rc.19: the rc.18 re-review-GO delta is the ACCEPTED BASELINE, and rc.19 adds ONLY the five resolutions below. Everything the rc.18 re-review certified GO carries forward UNTOUCHED (except bounded consistency replacements strictly required by the exact mission_tasks ACL change).
TARGET (bind these EXACT hashes; any drift voids this certification):
- RC19-DELTA.md sha256 efcdd13751d2e05072d058031a45ddb46b681ba516218c2b517be29240d29e0c (309 lines / 22970 B) — the PROPOSED contract delta against base head b0d78d8632c27d01cda3d30b0653716cf908e8ae, NOT committed.
- Regenerated PLAN.md sha256 8c72a5fb0956c08973deb86c58c05be82e2ecd4a51be62de6e4d164cd1029692 (469 lines / 48954 B).
- Accepted baseline (do NOT reopen): rc.18 delta 5c7da18f51cccc542037dfff2dc2e7cafc8b5f8fc4325f3d3c36b642c9db7b5e, rc.18 PLAN 488b48ec4af73e8b0762c23e728d970f0598d7c8d15d5224334e671120b681fd, rc.18 re-review GO 826319e0dab361caf49283ac35a02d1c8e5a16454cb5df8e3940659ce0f87062. Driving residual list: rc.18 red-team NO-GO b1b2f5f40cd7e8293524e620a728e00b399a7040cce3ac73a3df37ed1bc0c299.
- Base SSOT rc.16 at head b0d78d86 in docs/native-kanban-sot/, contracts/kanban-schema.v1.ts, code ground truth packages/db/src/schema.ts + packages/db/drizzle/** (latest 0016) + packages/storage/src/migrate-tier.ts.
CERTIFY (each item PASS or FAIL with file + sub-card citation) — the FIVE residuals:
1. B1(a) RAW-SINK: the raw-SQL mission_tasks.status writer sink (public storage exports / raw sink) is mapped to a FROZEN owner card OR an explicit justified compatibility exception, zero-remainder, WITH a negative test proving no unowned raw path can mutate status. FAIL if any raw path remains unowned or the negative test is absent/thin.
2. B1(b) GRANTS: the exact grant set backing every mapped writer is enumerated and PINNED; NO implicit or ambient grant may satisfy a mapping. FAIL if any mapping relies on an unstated/ambient grant.
3. B1(c) W13 EQUALITY: writer W13 mapping is internally consistent — ONE coherent model, not two contradictory equalities; the prior scanner W13 rule contradicted the two-way zero-remainder equality by requiring a future nonexistent KBN-100 path. Confirm the delta states which side is AUTHORITATIVE and removes the contradiction. FAIL if the contradiction persists.
4. B2(d) PRE-MAIN LOADER-INJECTION: the code-injection surface that can execute BEFORE main() in the migrator entrypoint (loader/init path) is closed by a named mechanism. FAIL if the surface remains open or the mechanism is unspecified.
5. B2(e) DIRECT-UID-10003 WRAPPER-BYPASS: identity enforcement HOLDS when the migrator is invoked directly as UID 10003 WITHOUT the wrapper — enforcement does NOT depend solely on the wrapper being in the call path. Confirm ONE coherent model that survives wrapper-absent invocation. FAIL if enforcement can be bypassed by skipping the wrapper.
ALSO CERTIFY:
6. SCOPE DISCIPLINE: the amendment changed NOTHING beyond the five residuals and the bounded consistency replacements strictly required by the mission_tasks ACL change. Walk every delta line; any change outside is a FAIL (scope-creep) + STOP+escalate.
7. BASELINE PRESERVED + T2/T3 UNDISTURBED: every rc.18-re-review-GO item carries forward untouched — T2 (KBN-101-03 owns 0017), T3 (07-before-06), first card KBN-101-00, RT-003..006, head-binding, rc.17 A-2 container surface, KBN-099. FAIL if any is perturbed beyond the required bounded consistency replacement.
8. IMPLEMENTATION-READINESS + HEAD/HASH BINDING: KBN-101-00, KBN-099, and every dependency-ready card are buildable WITHOUT any further contract change; and you reviewed the EXACT hashes above at base head b0d78d86. Name any card still needing a contract change.
OUTPUT (REREVIEW-rc19.md): VERDICT one of GO / GO-WITH-FIXES / NO-GO; a per-item PASS/FAIL table with citations; any FAIL needing a further contract change = NO-GO plus STOP+escalate to the coordinator. Builder fanout requires BOTH your GO and the red-team GO. This runs IN PARALLEL with the adversarial red-team.
STOP-CONDITION AWARENESS (coordinator, updated): this is the LAST authorized within-class refinement round. If a residual is still unresolved within B1/B2 after this round, that is a convergence-failure signal escalating the B1/B2 ENVELOPE itself to the human as underspecified — so certify strictly and completely. Separately, a THIRD distinct NEW defect CLASS (not a B1/B2 residual) = flag a contract-design escalation.
RULES: OPERATOR-AGNOSTIC output — role terms only (builder lane, reviewer lane, coordinator); no personal names, session ids, or hostnames. Cite file paths and sub-card ids; prefer tables. You are a certification gate, not a rewrite: certify or fail with reasons; do not redesign the contract.
===== END RE-REVIEW BRIEF =====
===== BEGIN VERBATIM rc.19 RED-TEAM BRIEF (-> kbn-redteam-sol) =====
You are the ADVERSARIAL RED-TEAM agent for the native Mosaic Kanban mission, FOURTH ROUND (rc.19 narrow residual-tightening) — an INDEPENDENT skeptic, a SEPARATE instance from the amendment author AND from the re-reviewer. You are NOT a builder. Assume the amendment is wrong until proven otherwise. Work read-only. This round adversarially tests a NARROW amendment authorized to resolve EXACTLY five named residuals within B1/B2 on top of the accepted rc.18 re-review-GO baseline. Write your verdict to REDTEAM-rc19.md in your working dir. Do NOT overwrite prior-round REDTEAM artifacts.
CONTEXT — you (red-team) returned rc.18 NO-GO at sha256 b1b2f5f40cd7e8293524e620a728e00b399a7040cce3ac73a3df37ed1bc0c299 with FIVE residuals all WITHIN B1/B2 (no third class). The coordinator ruled CONTINUE to rc.19, taking the rc.18 re-review-GO delta (826319e0) as accepted baseline and adding ONLY the five resolutions below. Your job: verify each residual is ACTUALLY and COMPLETELY closed, and hunt for any bypass that survives the fix.
TARGET (bind these EXACT hashes; drift voids this verdict):
- RC19-DELTA.md sha256 efcdd13751d2e05072d058031a45ddb46b681ba516218c2b517be29240d29e0c (309 lines / 22970 B) — PROPOSED delta vs base head b0d78d8632c27d01cda3d30b0653716cf908e8ae, NOT committed.
- Regenerated PLAN.md sha256 8c72a5fb0956c08973deb86c58c05be82e2ecd4a51be62de6e4d164cd1029692 (469 lines / 48954 B).
- Accepted baseline: rc.18 delta 5c7da18f51cccc542037dfff2dc2e7cafc8b5f8fc4325f3d3c36b642c9db7b5e, rc.18 re-review GO 826319e0dab361caf49283ac35a02d1c8e5a16454cb5df8e3940659ce0f87062. Prior red-team NO-GO b1b2f5f40cd7e8293524e620a728e00b399a7040cce3ac73a3df37ed1bc0c299 (your driving residual list).
- Base SSOT rc.16 at head b0d78d86; contracts/kanban-schema.v1.ts; code ground truth packages/db/src/schema.ts + packages/db/drizzle/** (latest 0016) + packages/storage/src/migrate-tier.ts.
ADVERSARIAL AXES — attack each residual; it is closed ONLY if you cannot break it:
1. B1(a) RAW-SINK. Independently sweep for ANY raw-SQL mission_tasks.status writer path (public storage exports, raw sink, any ORM bulk/upsert, any raw execute). Is EVERY raw path mapped to a frozen owner OR an explicit justified exception with ZERO remainder? Attack the exception: can it mutate status on an existing row? Attack the negative test: does it actually bite, or is it aspirational?
2. B1(b) GRANTS. Is the grant set backing every mapped writer enumerated and PINNED, with NO implicit/ambient grant satisfying a mapping? Hunt an ambient/inherited/default grant that lets an unmapped principal write status. Confirm the runtime role cannot write status via an unpinned grant.
3. B1(c) W13 EQUALITY. Is the W13 mapping now ONE coherent model, contradiction removed? Verify the authoritative side is stated and that no residual reference to a nonexistent future KBN-100 path remains. Attack for a NEW inconsistency introduced by the fix.
4. B2(d) PRE-MAIN LOADER-INJECTION. Is the pre-main() code-injection surface in the migrator entrypoint actually closed? Hunt any remaining loader/init/preload/constructor/env-driven path that executes before main(). Confirm the named mechanism genuinely prevents it, not just documents it.
5. B2(e) DIRECT-UID-10003 WRAPPER-BYPASS. Invoke the migrator directly as UID 10003 WITHOUT the wrapper in your threat model: does identity enforcement STILL hold? Confirm enforcement is in-process/fail-closed at connect time and does NOT depend on the wrapper being in the call path. Hunt a bypass: any path that connects to the DB with the wrapper absent and enforcement not asserted.
ALSO ATTACK:
6. SCOPE-CREEP. Did the amendment change ANYTHING beyond the five residuals + the bounded consistency replacements strictly required by the mission_tasks ACL change? Any out-of-scope edit = blocker + STOP+escalate. Diff line by line.
7. BASELINE/T2/T3 REGRESSION + NEW-DEFECT. Confirm no rc.18-GO item was perturbed (0017 slot, 07-before-06, KBN-099 placement/DB-only, RT-003..006, A-2 surface). Does closing any residual introduce a NEW security or sequencing defect (new fail-open, new DDL entrypoint, new slot collision, new confused-deputy)? Is KBN-101-00 still the safe first card?
OUTPUT (REDTEAM-rc19.md): VERDICT one of GO / GO-WITH-FIXES / NO-GO; a DEFECT TABLE (id, axis, severity blocker/major/minor, sub-card, concrete failure, minimal fix); CONFIRMATIONS of what you actively verified SOUND; any blocker unfixable without a further contract change = NO-GO + STOP+escalate. If artifacts are missing/incomplete/inconsistent, return NO-GO rather than guessing. Builder fanout requires BOTH your GO and the re-review GO; runs IN PARALLEL with re-review.
STOP-CONDITION AWARENESS (coordinator, updated + CRITICAL): this is the LAST authorized within-class refinement round. If you again return non-GO with residuals STILL confined to B1/B2 (i.e. a SECOND consecutive within-class non-converging round), that itself is the convergence-failure signal — say so explicitly: it escalates the B1/B2 ENVELOPE to the human as UNDERSPECIFIED rather than triggering yet another patch round. Distinguish clearly in your verdict: (i) residuals fully closed = GO; (ii) still-open B1/B2 residuals = NO-GO that escalates the envelope as underspecified; (iii) a THIRD distinct NEW defect CLASS = contract-design escalation. Be precise about which case you are in.
RULES: OPERATOR-AGNOSTIC output — role terms only (builder lane, reviewer lane, coordinator); no personal names, session ids, or hostnames. Be concrete: cite file paths and sub-card ids, prefer tables. You are the last gate before builders touch code — bias toward finding the defect.
===== END RED-TEAM BRIEF =====