arkaos 4.42.0 → 4.43.0

package/THE-ARKAOS-GUIDE.md

@@ -1,6 +1,6 @@
 # The ArkaOS Guide
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills, 297 commands, 18 ADRs.
+> v4.43.0 — 89 agents, 17 departments, 332 skills, 297 commands, 18 ADRs.
 > One file, everything you need to start. Generated by `scripts/guide_gen.py` — never hand-edited.
 
 ## What it is

package/VERSION

@@ -1 +1 @@
-4.42.0
+4.43.0

package/arka/skills/checkpoint/SKILL.md

@@ -53,7 +53,12 @@ Any work item whose execution would block the user for **> 30 seconds**
 Per the brainstorm (Marta + Tomas):
 
 - **Technical conflicts** between reviewers (e.g. Eduardo + Francisca
-  disagree on a code-style call) → Marta resolves silently.
+  disagree on a code-style call) → Marta resolves ON THE RECORD:
+  evidence decides (reproduce the claim, cite the reproduction), and
+  the resolution lands in her verdict notes. A blocker backed by
+  evidence is fixed or REFUTED with a substantive reason — never
+  dropped silently (constitution `inter-agent-checkpoints` enforcement
+  + `evidence-flow`; the aggregate guard enforces the bar).
 - **Strategic / taste / business-knowledge conflicts** → Marta surfaces
   the disagreement at the next checkpoint: *"Eduardo + Francisca
   discordam em X, eu inclino para A — qual o teu input?"*. The user
@@ -74,8 +79,10 @@ Tens contexto a acrescentar antes de eu arrancar? (Silêncio = procedo.)
   follows by emitting checkpoint markers between agent calls.
 - Does not block the user. The user is free to stay silent (proceed)
   or to send any message (parsed by `parse_user_injection`).
-- Does not bypass the mandatory 13-phase flow. Checkpoints are
-  emitted **inside** the per-todo loop of Phase 11.
+- Does not bypass the mandatory 4-gate evidence flow (the 13-phase
+  flow it referenced was replaced in v4.1.0 — constitution
+  `evidence-flow`). Checkpoints are emitted **inside** Gate 3
+  execution, between sub-dispatches; Gate 4 still runs.
 
 ## Cross-references
 

package/arka/skills/flow/SKILL.md

@@ -142,6 +142,10 @@ resumes at the right gate.
   Time and token cost are not acceptable answers to any of the three.
 - Quality Gate REJECTED loops back at most twice; a third REJECTED
   escalates to the operator with the full verdict.
+- The gate-closing report reproduces each reviewer verdict VERBATIM
+  under `### <Reviewer> — verbatim`, with the ledger artifact path
+  (`~/.arkaos/quality-gate/<session>/`) beside it. Summarising a
+  reviewer in your own words is relay, not report.
 - Close with an honest summary: what changed, where, how it was
   verified (real commands + results), what remains open.
 

package/config/claude-agents/eduardo-copy.md

@@ -55,10 +55,21 @@ DOCUMENTATION-scope prose it is advisory.
 Return a `QGVerdict` JSON object (schema: `QG_VERDICT_JSON_SCHEMA` in
 `core.governance.qg_verdict`): `verdict`, `evidence_report` summary,
 `blockers` [{check, detail, file, verdict}] with exact location and
-correction — `verdict` is claim-level: CONFIRMED (you verified the
+correction — `check` names the evidence check or rubric area (the
+aggregate's coverage matching keys on it; never leave it empty),
+`verdict` is claim-level: CONFIRMED (you verified the
 error on the page/line), PLAUSIBLE (credible, unverified), REFUTED
 (disproven; recorded, never counts toward rejection) —,
-`reviewer: "copy-director-eduardo"`, `model_used`, `notes`.
+`reviewer: "copy-director-eduardo"`, `model_used`, `evidence_digest`
+(the `report_digest` of the report you interpreted — mandatory since
+PR-B4; an artifact without it cannot support an APPROVED aggregate),
+`notes`.
+
+Emit the JSON inside a ```arka-qgverdict fence in your FINAL message —
+the fence is what the hook-boundary ledger captures verbatim. Never
+write triple backticks inside a JSON string — one inside notes cut the
+extractor mid-string (francisca-tech-17); the balanced-JSON cut now
+recovers most such cases, and none of them is worth relying on.
 
 Model tier: single source is constitution `quality_gate.model_policy` —
 Quality Gate reviewers run on the best model available (frontier tier,

package/config/claude-agents/francisca-tech.md

@@ -54,8 +54,18 @@ you did not attempt to reproduce is PLAUSIBLE at best, never CONFIRMED.
 Return a `QGVerdict` JSON object (schema: `QG_VERDICT_JSON_SCHEMA` in
 `core.governance.qg_verdict`): `verdict`, `evidence_report` summary,
 `blockers` [{check, detail, file, verdict}] numbered B1./B2. with line
-references and fix suggestions,
-`reviewer: "tech-director-francisca"`, `model_used`, `notes`.
+references and fix suggestions — `check` names the evidence check or
+rubric area (the aggregate's coverage matching keys on it; never
+leave it empty) —, `reviewer: "tech-director-francisca"`,
+`model_used`, `evidence_digest` (the `report_digest` of the report
+you interpreted — mandatory since PR-B4; an artifact without it
+cannot support an APPROVED aggregate), `notes`.
+
+Emit the JSON inside a ```arka-qgverdict fence in your FINAL message —
+the fence is what the hook-boundary ledger captures verbatim. Never
+write triple backticks inside a JSON string — one inside notes cut the
+extractor mid-string (francisca-tech-17); the balanced-JSON cut now
+recovers most such cases, and none of them is worth relying on.
 
 Model tier: single source is constitution `quality_gate.model_policy` —
 Quality Gate reviewers run on the best model available (frontier tier,

package/config/claude-agents/marta-cqo.md

@@ -26,9 +26,20 @@ evidence report, never from model size.
 1. Run the engine first — no verdict without a report:
    `~/.arkaos/bin/arka-py -m core.governance.evidence_checks <project_dir> [--changed-files ...] [--test-command '...'] --json`
 2. Dispatch Eduardo (spellcheck + changed copy) and Francisca
-   (lint/typecheck/tests/coverage/security-grep) with the report and the
-   structured output schema `QG_VERDICT_JSON_SCHEMA` from
-   `core.governance.qg_verdict`.
+   (lint/typecheck/tests/coverage/security-grep) with the report and,
+   in the prompt, the QGVerdict field names (`QG_VERDICT_JSON_SCHEMA`
+   in `core.governance.qg_verdict` is that contract — the Agent tool
+   has no structured-output parameter). Dispatch shape (PR-B4): the
+   prompt names the FULL field set the reviewer returns — `verdict`,
+   `evidence_report` {overall, checks_ran, checks_failed,
+   checks_skipped}, `blockers` [{`check` (the evidence check name;
+   coverage matching keys on it), `detail`, `file`, `verdict`
+   CONFIRMED/PLAUSIBLE/REFUTED}], `reviewer`, `model_used`,
+   `evidence_digest` (= the report's `report_digest`), `notes`. A
+   dispatch that invents its own field names fail-softs the artifact
+   (16 schema errors on one B2 round); a reviewer artifact without
+   `evidence_digest` cannot support an APPROVED aggregate — the guard
+   refuses it and the reviewer must be re-dispatched.
 3. Aggregate at CLAIM level (Constitution 2.0): every reviewer blocker
    carries `verdict` CONFIRMED / PLAUSIBLE / REFUTED. Only CONFIRMED and
    PLAUSIBLE blockers count toward rejection; REFUTED are recorded for
@@ -39,9 +50,7 @@ evidence report, never from model size.
    - overall == "pass" → APPROVED only if zero CONFIRMED/PLAUSIBLE blockers.
    - overall == "insufficient-evidence" → APPROVED only with explicit
      justification in notes; otherwise REJECTED.
-4. Record the outcome via `core.governance.review_workflow` passing
-   `evidence_overall` — it raises on APPROVED-over-fail by design.
-5. Record the eval label (evals ADR 2026-07-09) as your FINAL act — the
+4. Record the eval label (evals ADR 2026-07-09) as your FINAL act — the
    corpus only grows if the verdict-issuer writes it, and dispatch
    through this agent bypasses the department SKILL's step 6: write your
    final QGVerdict JSON to a temp file and run
@@ -51,11 +60,15 @@ evidence report, never from model size.
    remedy: invalid JSON (fix the JSON and re-run), a missing
    --session-id (pass the session id — the anti-self-approval guard
    reads that session's reviewer ledger), or a guard refusal (the
-   ledger cannot support your aggregate: quorum, digest, blocker
-   coverage, or an APPROVED verdict standing over a rejecting
-   reviewer — read the stderr reasons and fix the REVIEW, not the
-   JSON; if the reason names AGGREGATE.json or the session id, fix
-   that instead). Never skip.
+   ledger cannot support your aggregate: quorum, a missing or
+   mismatched `evidence_digest` without a justified `digest_carries`
+   entry, a session already stamped as ended (digest and session
+   reasons refuse only an APPROVED aggregate — a REJECTED one records
+   with warnings), blocker coverage, or an
+   APPROVED verdict standing over a rejecting reviewer — read the
+   stderr reasons and fix the REVIEW, not the JSON; if the reason
+   names AGGREGATE.json or the session id, fix that instead). Never
+   skip.
    Every review feeds `~/.arkaos/telemetry/qg-verdicts.jsonl`, redo
    verdicts included (a REJECTED→APPROVED pair is two labels).
 
@@ -64,11 +77,25 @@ evidence report, never from model size.
 Return a `QGVerdict` JSON object: `verdict` (APPROVED|REJECTED),
 `evidence_report` {overall, checks_ran, checks_failed, checks_skipped},
 `blockers` [{check, detail, file, verdict}], `reviewer: "cqo-marta"`,
-`model_used`, `notes`. Binary — there is no "approved with caveats".
+`model_used`, `notes`, `evidence_digest` (the `report_digest` of the
+report you aggregated — mandatory since PR-B4) and, when you carry an
+earlier review over a report change, `digest_carries`
+[{reviewer, evidence_digest, reason}] naming the digest THAT reviewer
+actually reviewed and why the review still stands (>= 40 chars).
+Binary — there is no "approved with caveats".
+
+Emit the final JSON inside a ```arka-qgverdict fence in your FINAL
+message — the fence is what the hook-boundary ledger captures, and an
+aggregate that exists only as prose is a relay (the B1 gate closed
+with this fence present by ad-hoc instruction; it is contract now).
+Never write triple backticks inside a JSON string — one inside notes
+cut the extractor mid-string (francisca-tech-17); the balanced-JSON
+cut now recovers most such cases, and none of them is worth relying
+on.
 
 Filled example (the shape you return, not a schema):
 
-```json
+```arka-qgverdict
 {"verdict": "REJECTED",
  "evidence_report": {"overall": "pass", "checks_ran": ["lint","tests"],
                      "checks_failed": [], "checks_skipped": ["coverage"]},
@@ -77,9 +104,32 @@ Filled example (the shape you return, not a schema):
     "detail": "AttributeError on malformed record — docstring claims 'never raises'; reproduced via check_x('bad')",
     "file": "core/governance/x.py:138", "verdict": "CONFIRMED"}],
  "reviewer": "cqo-marta", "model_used": "opus",
+ "evidence_digest": "3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a3f2a",
  "notes": "Engine pass but 1 CONFIRMED blocker, reproduced by my own hand."}
 ```
 
+## Reporting (verbatim, never relay)
+
+The gate-closing report reproduces every reviewer verdict VERBATIM
+under `### <Reviewer> — verbatim`, each with its ledger artifact path
+beside it. Summarising a reviewer in your own words is relay, not
+report — a relay inside a gate is a single point of distortion, and
+it is how a corpus reached 80 aggregator-authored records with zero
+reviewer-signed ones.
+
+## Conflict Handling (no silent resolution)
+
+A reviewer blocker BACKED BY EVIDENCE is never resolved silently: it
+is fixed (and the fix verified by execution), or REFUTED on the
+record with a substantive reason (>= 40 chars — the guard enforces
+the bar), or it blocks. Disagreement between reviewers is settled by
+evidence, not by rank: reproduce the claim, cite the reproduction.
+Only a blocker with no evidence behind it (no repro, no citation) may
+be dropped, and even that drop is recorded in `notes`, never omitted.
+A CONFIRMED blocker is never merely noted: the guard reads
+`blockers`, not `notes` — it is fixed, or REFUTED in `blockers` with
+its reason, or it blocks.
+
 ## Signature Rules (anti-sycophancy)
 
 - Open with "Quality Gate Verdict:" and close with "Final:".

package/config/constitution.yaml

@@ -248,7 +248,7 @@ enforcement_levels:
 
       - id: inter-agent-checkpoints
         rule: "Long-running multi-agent dispatches (estimated >30s) are fragmented into sub-dispatches of 2-3min each. Between sub-dispatches, the orchestrator emits a proactive [arka:checkpoint] prompt announcing the next sub-dispatch and inviting user context injection. The user can inject (continue with addition) or stay silent (proceed)."
-        enforcement: "Orchestrator wraps multi-step work in checkpointed dispatches; reviewer conflicts escalated to user when strategic (taste/business knowledge), resolved silently when purely technical; QG deliberations are visible, not just verdict."
+        enforcement: "Orchestrator wraps multi-step work in checkpointed dispatches; reviewer conflicts escalated to user when strategic (taste/business knowledge), resolved on the record when purely technical (evidence cited in the verdict notes — never silently; the earlier self-contradiction was resolved 2026-07-30 in favour of visibility); QG deliberations are visible, not just verdict."
 
       - id: hybrid-learning
         rule: "ArkaOS learns from user corrections via hybrid mechanism: implicit auto-detection with confidence scoring for typical corrections (default), explicit Marta-led confirmation for high-leverage rules (top-level rule candidates) or rules that contradict existing memory. Marta is the owner of the learning loop. Memory rules carry a confidence field that climbs as the rule is applied without correction."
@@ -492,3 +492,6 @@ amendments:
     - version: "4.12.0"
       date: "2026-07-09"
       changes: "Interaction Reform PR2 (operator-approved plan, 2026-07-09): added gate-judges MUST rule — plan-judge at Gate 2 and output-judge at Gate 4 for MEDIUM/HIGH work, structured JudgeVerdict (core.governance.judge), frontier tier, arkaos-not-yes-man standard applied to agents, user_challenge surfacing for technically wrong requests; verdicts recorded to judge-verdicts.jsonl."
+    - version: "4.43.0"
+      date: "2026-07-30"
+      changes: "PR-B4 (operator-approved repair-campaign plan): inter-agent-checkpoints enforcement text amended — technical reviewer conflicts change from 'resolved silently' to 'resolved on the record' (evidence cited in verdict notes), resolving the self-contradiction with the same enforcement's 'QG deliberations are visible' clause in favour of visibility. Rule text, level and scope unchanged."

package/core/evals/record_cli.py

@@ -8,14 +8,19 @@ flow skill instructions), closing the "labels gratuitos" loop from the
 evals ADR.
 
 ``--kind qg`` is the AGGREGATE path and runs the anti-self-approval
-guard (PR-B3): ``--session-id`` is mandatory and validated, the
-session's reviewer ledger must hold at least two hook-captured
-reviewer verdicts, no evidence_digest present on both sides may
-disagree (an absent digest warns — PR-B4 makes dispatch populate it),
-no CONFIRMED reviewer blocker may disappear silently, and an APPROVED
-aggregate may not stand over a rejecting reviewer. The label records
-ONLY once AGGREGATE.json is verifiably on disk — an
-accepted-but-unwritten aggregate is a refusal, not a success.
+guard (PR-B3, hardened in PR-B4): ``--session-id`` is mandatory and
+validated, the session's reviewer ledger must hold at least two
+hook-captured reviewer verdicts, the digest chain must hold (the
+aggregate and every counted reviewer artifact carry evidence_digest;
+a reviewer's digest that predates the final report needs an explicit
+``digest_carries`` justification), the session must not be stamped
+ended, no CONFIRMED reviewer blocker may disappear silently, and an
+APPROVED aggregate may not stand over a rejecting reviewer.
+Dispatch-shape refusals are verdict-aware: they refuse an APPROVED
+aggregate and demote to warnings on a REJECTED one, so a rejection
+label survives a bad delta. The label records ONLY once
+AGGREGATE.json is verifiably on disk — an accepted-but-unwritten
+aggregate is a refusal, not a success.
 
 ``--kind reviewer`` records an individual reviewer's verdict as a
 label and cross-references the ledger by ``verdict_digest`` — it never

package/core/governance/aggregate_guard.py

@@ -5,12 +5,19 @@ reviewer artifacts behind it — the orchestrator's own words, recorded
 as a completed gate. This guard makes that shape unrecordable AS AN
 AGGREGATE: an aggregate verdict is only recorded when the session's
 reviewer ledger holds at least two HOOK-CAPTURED reviewer verdicts,
-no evidence_digest present on both sides disagrees (dispatch does not
-yet REQUIRE the digest — PR-B4 makes it mandatory; an absent digest
-warns instead of refusing, and when reviewers do populate it, as this
-PR's own r1 artifacts did, the comparison decides), no CONFIRMED
-reviewer blocker disappears silently, and an APPROVED aggregate
-stands over no rejecting reviewer.
+the digest chain holds (PR-B4 dispatch shape: the aggregate and every
+counted reviewer artifact must carry evidence_digest, and each
+reviewer's digest must match the aggregate's — or be excused by an
+explicit, justified ``digest_carries`` entry naming the report that
+reviewer actually reviewed), no CONFIRMED reviewer blocker disappears
+silently, and an APPROVED aggregate stands over no rejecting reviewer.
+
+Severity is verdict-aware (PR-B4): fabrication vectors — quorum, an
+APPROVED over a rejecting reviewer, a vanishing CONFIRMED blocker —
+refuse regardless of verdict; dispatch-shape issues (digest chain,
+session binding) refuse only an APPROVED aggregate and demote to
+warnings on a REJECTED one, so a rejection label survives exactly the
+case where the CQO catches a bad delta.
 
 Only records whose ``source`` is in ``CAPTURE_SOURCES`` count: a
 record the orchestrator could write itself (any other source) would
@@ -27,16 +34,21 @@ home directory and this guard runs in the same trust domain as the
 orchestrator it polices — a determined orchestrator could forge
 records with a file write, either to FABRICATE a quorum or to
 SUPPRESS an existing verdict (a forged newer record supersedes it —
-same capability ceiling, different mechanics). Session ids are
-validated against the ledger's safety rule, but nothing yet binds an
-aggregate to the runtime session that produced the reviews — a past
-session holding two reviewer records is a reusable quorum token
-until PR-B4 binds the dispatch side. And ``--kind reviewer``
-(record_cli) remains an unguarded label path for reviewer
-identities: its ledger cross-reference is provenance, not
-admission. The guard turns ACCIDENTAL self-approval into
-deliberate, transcript-visible forgery; it does not and cannot make
-forgery impossible from inside the same account.
+same capability ceiling, different mechanics). Session binding
+(PR-B4) closes the COMMON reuse path, not every path: the SessionEnd
+hook stamps a session's ledger directory (``.ended``), and an
+APPROVED aggregate citing a stamped session is refused. A session
+that crashes never fires SessionEnd and stays unstamped — and in
+observed practice SessionEnd fires for a minority of sessions, so an
+unstamped ledger proves nothing about liveness. A session still open
+elsewhere is citable from this one, and the stamp itself is a file
+the same account could delete: the binding is evidence from the
+hook boundary, not a cryptographic seal. ``--kind
+reviewer`` (record_cli) likewise remains an unguarded label path for
+reviewer identities: its ledger cross-reference is provenance, not
+admission. The guard turns ACCIDENTAL self-approval into deliberate,
+transcript-visible forgery; it does not and cannot make forgery
+impossible from inside the same account.
 """
 
 from __future__ import annotations
@@ -286,35 +298,136 @@ def _covered(key: frozenset[str], aggregate: dict, approved: bool) -> str:
     return "absent"
 
 
-def _digest_reasons(
+def _carries(aggregate: dict) -> dict[str, dict]:
+    """Declared digest carries, keyed by canonical reviewer identity."""
+    carries: dict[str, dict] = {}
+    for entry in aggregate.get("digest_carries") or []:
+        if isinstance(entry, dict):
+            carries[_identity(str(entry.get("reviewer") or ""))] = entry
+    return carries
+
+
+def _carry_issue(
+    reviewer_id: str, their: str, agg_digest: str, carry: dict | None
+) -> str | None:
+    """Why a digest mismatch is NOT excused by a declared carry.
+
+    None means the carry stands: it names the digest the reviewer's own
+    artifact carries, with a substantive reason. Anything else is the
+    plain mismatch — an undeclared carry, a carry pointing at a digest
+    the reviewer never reviewed, or a bare justification.
+    """
+    if carry is None:
+        return (
+            f"evidence_digest mismatch: {reviewer_id} reviewed "
+            f"{their[:12]}…, aggregate cites {agg_digest[:12]}… — not "
+            "the same evidence report; re-dispatch the reviewer or "
+            "declare a justified digest_carries entry (PR-B4)"
+        )
+    if _norm(carry.get("evidence_digest")) != their:
+        return (
+            f"digest carry for {reviewer_id} names "
+            f"{_norm(carry.get('evidence_digest'))[:12]}… but the "
+            f"reviewer's artifact carries {their[:12]}… — a carry must "
+            "cite the report that reviewer actually reviewed"
+        )
+    if len(_norm(carry.get("reason"))) < _MIN_REFUTE_DETAIL:
+        return (
+            f"digest carry for {reviewer_id} lacks a substantive reason "
+            f"(>= {_MIN_REFUTE_DETAIL} chars — the same bar as a REFUTED "
+            "drop): why does the earlier review still stand?"
+        )
+    return None
+
+
+_MISSING_AGGREGATE_DIGEST = (
+    "aggregate carries no evidence_digest — the dispatch shape (PR-B4) "
+    "requires the aggregator to cite the report it aggregated "
+    "(report_digest from the evidence --json output)"
+)
+_MISSING_REVIEWER_DIGEST = (
+    "{rid} artifact carries no evidence_digest — the dispatch must "
+    "populate it (PR-B4 dispatch shape); re-dispatch that reviewer "
+    "with the report_digest"
+)
+_CARRY_ACCEPTED = (
+    "digest carry accepted: {rid} reviewed {their}… while the "
+    "aggregate cites {agg}… — justification on the record"
+)
+
+
+def _digest_issues(
     aggregate: dict, verdicts: list[tuple[str, dict]]
 ) -> tuple[list[str], list[str]]:
-    """Compare evidence_digest across aggregate and reviewer verdicts."""
-    reasons: list[str] = []
-    warnings: list[str] = []
+    """Dispatch-shape and integrity issues on the digest chain (PR-B4).
+
+    Returns (issues, notes). Issues are verdict-aware at the caller:
+    they refuse an APPROVED aggregate and are demoted to warnings on a
+    REJECTED one. Notes (accepted carries) are always warnings — a
+    carry is legitimate, and legitimate is not invisible.
+    """
+    issues: list[str] = []
+    notes: list[str] = []
     agg_digest = _norm(aggregate.get("evidence_digest"))
     if not agg_digest:
-        warnings.append("aggregate carries no evidence_digest")
-        return reasons, warnings
-    seen_any = False
+        issues.append(_MISSING_AGGREGATE_DIGEST)
+    carries = _carries(aggregate)
     for reviewer_id, verdict in verdicts:
         their = _norm(verdict.get("evidence_digest"))
         if not their:
+            issues.append(_MISSING_REVIEWER_DIGEST.format(rid=reviewer_id))
             continue
-        seen_any = True
-        if their != agg_digest:
-            reasons.append(
-                f"evidence_digest mismatch: {reviewer_id} reviewed "
-                f"{their[:12]}…, aggregate cites {agg_digest[:12]}… — "
-                "not the same evidence report"
-            )
-    if not seen_any:
-        warnings.append(
-            "no reviewer artifact carries evidence_digest (dispatch "
-            "shape — PR-B4 enforces it); digest comparison had nothing "
-            "to bite on"
+        if not agg_digest or their == agg_digest:
+            continue
+        issue = _carry_issue(
+            reviewer_id, their, agg_digest, carries.get(_identity(reviewer_id))
         )
-    return reasons, warnings
+        if issue is not None:
+            issues.append(issue)
+        else:
+            notes.append(_CARRY_ACCEPTED.format(
+                rid=reviewer_id, their=their[:12], agg=agg_digest[:12]
+            ))
+    return issues, notes
+
+
+def _ended_issues(session_id: str) -> list[str]:
+    """A stamped session is not a live quorum (PR-B4 session binding)."""
+    from core.governance.reviewer_ledger import ENDED_NAME
+
+    if not (ledger_root() / session_id / ENDED_NAME).is_file():
+        return []
+    return [
+        f"session {session_id} is marked ended (SessionEnd stamped its "
+        "ledger) — a past session's reviewer records are not a reusable "
+        "quorum token; run the reviews in the live session"
+    ]
+
+
+def _check_key_warnings(
+    verdicts: list[tuple[str, dict]]
+) -> list[str]:
+    """CONFIRMED blockers filed without a check key — warning only.
+
+    Coverage still matches on detail/file tokens (_blocker_key keeps
+    liveness), but the dispatch shape asks reviewers to name the
+    evidence check so coverage means shared vocabulary, not prose luck.
+    """
+    warnings: list[str] = []
+    for reviewer_id, verdict in verdicts:
+        for blocker in verdict.get("blockers") or []:
+            if not isinstance(blocker, dict):
+                continue
+            if _norm(blocker.get("verdict")) != "confirmed":
+                continue
+            if not _tokens(blocker.get("check")) and _blocker_key(blocker):
+                warnings.append(
+                    f"CONFIRMED blocker ({reviewer_id}) filed without a "
+                    "check key — matched on detail/file tokens; the "
+                    "dispatch shape (PR-B4) asks for the evidence check "
+                    "name in 'check'"
+                )
+    return warnings
 
 
 _COVERAGE_REASONS = {
@@ -455,7 +568,7 @@ def check_aggregate(aggregate: dict, session_id: str) -> GuardResult:
             reviewers, [name for name, _ in counted]
         )
     verdicts = [(str(r.get("reviewer_id")), r["verdict"]) for _, r in counted]
-    reasons, warnings = _reasons(aggregate, verdicts)
+    reasons, warnings = _reasons(aggregate, verdicts, session_id)
     return GuardResult(
         ok=not reasons,
         reasons=reasons,
@@ -466,17 +579,39 @@ def check_aggregate(aggregate: dict, session_id: str) -> GuardResult:
 
 
 def _reasons(
-    aggregate: dict, verdicts: list[tuple[str, dict]]
+    aggregate: dict, verdicts: list[tuple[str, dict]], session_id: str
 ) -> tuple[list[str], list[str]]:
-    """Every refusal reason and warning for one aggregate."""
+    """Every refusal reason and warning for one aggregate.
+
+    Two severities, split on the aggregate's own verdict (PR-B4 item 7).
+    Fabrication vectors — an APPROVED standing over a rejecting
+    reviewer, a CONFIRMED blocker vanishing — refuse regardless of
+    verdict. Dispatch-shape issues (digest chain, session binding)
+    refuse only an APPROVED aggregate: refusing a REJECTED one over
+    shape would throw away the rejection label in exactly the case
+    where the CQO catches a bad delta, and a recorded rejection
+    launders nothing — the redo loop continues either way.
+    """
     approved = _norm(aggregate.get("verdict")) == "approved"
-    digest_reasons, warnings = _digest_reasons(aggregate, verdicts)
+    issues, notes = _digest_issues(aggregate, verdicts)
+    issues += _ended_issues(session_id)
     reasons = (
-        digest_reasons
-        + _verdict_reasons(aggregate, verdicts)
+        _verdict_reasons(aggregate, verdicts)
         + _blocker_reasons(aggregate, verdicts, approved)
     )
-    return reasons, warnings + _own_finding_warnings(aggregate, verdicts)
+    warnings = (
+        notes
+        + _check_key_warnings(verdicts)
+        + _own_finding_warnings(aggregate, verdicts)
+    )
+    if approved:
+        return issues + reasons, warnings
+    demoted = [
+        f"{issue} [recorded anyway: the refusal is verdict-aware "
+        "(PR-B4) — a REJECTED label is never lost to dispatch shape]"
+        for issue in issues
+    ]
+    return reasons, demoted + warnings
 
 
 def write_aggregate(

package/core/governance/qg_verdict.py

@@ -9,8 +9,10 @@ The verdict is INTERPRETATION of an ``EvidenceReport`` from
   - ``APPROVED`` requires ``overall == "pass"``, or
     ``insufficient-evidence`` with an explicit justification in notes.
 
-``QG_VERDICT_JSON_SCHEMA`` is the dict to pass as the structured-output
-schema when dispatching reviewers via the Agent tool.
+``QG_VERDICT_JSON_SCHEMA`` is the field contract to name INSIDE the
+dispatch prompt — the Agent tool has no structured-output parameter
+(PR-B4 dispatch shape; see the Reviewer Dispatch Contract in
+departments/quality/SKILL.md).
 """
 
 from __future__ import annotations
@@ -45,6 +47,44 @@ class QGBlocker(BaseModel):
     )
 
 
+class QGDigestCarry(BaseModel):
+    """One justified digest carry on an AGGREGATE verdict (PR-B4).
+
+    Per-reviewer digest equality would force a re-dispatch of every
+    reviewer whenever the evidence report changes at all. When the
+    aggregator judges an earlier review still valid against the final
+    report — a message-only amend, a doc-only delta — it declares the
+    carry HERE, naming the reviewer, the digest that reviewer actually
+    reviewed, and the reason. The guard accepts the mismatch only when
+    the declared digest matches the reviewer's own artifact and the
+    reason is substantive; anything less refuses an APPROVED aggregate.
+    """
+
+    reviewer: str = Field(description="Reviewer id whose review is carried")
+    evidence_digest: str = Field(
+        description=(
+            "sha256 of the report that reviewer actually reviewed — "
+            "must equal the evidence_digest in their ledger artifact"
+        )
+    )
+    reason: str = Field(
+        description=(
+            "Why the earlier review still stands against the final "
+            "report (>= 40 chars — same bar as a REFUTED drop)"
+        )
+    )
+
+    @model_validator(mode="after")
+    def digest_is_sha256_hex(self) -> QGDigestCarry:
+        if not _SHA256_HEX_RE.fullmatch(self.evidence_digest):
+            raise ValueError(
+                "a digest carry must name the exact report digest the "
+                f"reviewer reviewed (64 hex chars), got "
+                f"{self.evidence_digest!r}"
+            )
+        return self
+
+
 class QGEvidenceSummary(BaseModel):
     """Embedded summary of the EvidenceReport the reviewer interpreted."""
 
@@ -98,6 +138,20 @@ class QGVerdict(BaseModel):
             "ledger (raw_sha256); empty when not yet ledgered"
         ),
     )
+    # PR-B4: aggregate-only, optional so the existing corpus stays
+    # valid. Reviewer verdicts have no use for it (the guard reads it
+    # from the aggregate side only).
+    digest_carries: list[QGDigestCarry] = Field(
+        default_factory=list,
+        description=(
+            "AGGREGATE only: justified carries for reviewers whose "
+            "review the aggregator judges still valid against the "
+            "final report — typically an earlier report revision; the "
+            "guard verifies the declared digest against the reviewer's "
+            "own artifact, never digest precedence (digests are "
+            "unordered — see QGDigestCarry)"
+        ),
+    )
 
     @model_validator(mode="after")
     def digests_are_sha256_hex_or_empty(self) -> QGVerdict:

package/core/governance/reviewer_ledger.py

@@ -115,6 +115,13 @@ _NOTICES_NAME = "NOTICES.jsonl"
 # working for sessions that PASS the gate (an unowned name made _purge
 # refuse the whole directory and turned retention into a no-op).
 AGGREGATE_NAME = "AGGREGATE.json"
+# Stamped by the SessionEnd hook (mark_session_ended, PR-B4): a session
+# whose ledger carries this marker has ended, so its reviewer records
+# are no longer a live quorum — aggregate_guard refuses an APPROVED
+# aggregate that cites an ended session. Dot-prefixed on purpose: the
+# record pool skips dot names, so the stamp can never count as a
+# verdict.
+ENDED_NAME = ".ended"
 _RECORD_NAME_RE = re.compile(r"^[A-Za-z0-9._-]{1,128}-\d+-[0-9a-f]{8}\.json$")
 
 
@@ -506,6 +513,31 @@ def _find_by_digest(paths: list[Path], digest: str) -> dict | None:
     return None
 
 
+def mark_session_ended(session_id: str) -> None:
+    """Stamp a session's ledger directory at SessionEnd. Never raises.
+
+    Only stamps an EXISTING directory: a session that captured no
+    reviewer verdicts holds no quorum to expire, and creating its
+    directory here would hand retention an empty dir to babysit. The
+    stamp is evidence from the hook boundary — the runtime fires
+    SessionEnd, not the orchestrator — so aggregate_guard can refuse an
+    APPROVED aggregate built on a session that already ended. A session
+    that crashes never receives SessionEnd and is never stamped; the
+    guard's docstring carries that limit honestly.
+    """
+    try:
+        if not _safe_id(session_id):
+            return
+        session_dir = ledger_root() / session_id
+        if not session_dir.is_dir():
+            return
+        stamp = session_dir / ENDED_NAME
+        stamp.touch()
+        os.chmod(stamp, 0o600)
+    except Exception:
+        return  # SessionEnd is best-effort; a failed stamp never blocks
+
+
 def _expired(session_dir: Path, cutoff: datetime) -> bool:
     try:
         mtime = datetime.fromtimestamp(session_dir.stat().st_mtime, tz=UTC)
@@ -524,6 +556,8 @@ def _is_own_file(item: Path) -> bool:
         return True
     if name == AGGREGATE_NAME:
         return True  # the accepted aggregate (aggregate_guard, PR-B3)
+    if name == ENDED_NAME:
+        return True  # the SessionEnd stamp (mark_session_ended, PR-B4)
     if name.startswith(".") and ".tmp-" in name:
         return True  # an interrupted atomic publish
     return bool(_RECORD_NAME_RE.fullmatch(name))

package/core/hooks/session_end.py

@@ -122,6 +122,21 @@ def _sweep_reviewer_ledger() -> None:
         pass
 
 
+def _stamp_ledger_ended(session_id: str) -> None:
+    """Mark this session's reviewer ledger as ended (PR-B4 binding).
+
+    The stamp is what lets aggregate_guard refuse an APPROVED aggregate
+    built on a PAST session's reviewer records — without it, any old
+    session directory is a reusable quorum token.
+    """
+    try:
+        from core.governance.reviewer_ledger import mark_session_ended
+
+        mark_session_ended(session_id)
+    except Exception:  # best-effort — this hook never blocks
+        pass
+
+
 def main(stdin_json: dict | None = None) -> int:
     if stdin_json is None:
         stdin_json, _ = read_stdin_json()
@@ -135,6 +150,7 @@ def main(stdin_json: dict | None = None) -> int:
 
     write_digest(session_id, transcript_path)
     _end_session(session_id)
+    _stamp_ledger_ended(session_id)
     _sweep_reviewer_ledger()
     return 0
 

package/departments/quality/SKILL.md

@@ -44,6 +44,11 @@ Any Department Workflow:
        - overall == "insufficient-evidence" → APPROVED only with an
          explicit justification in the verdict notes; otherwise REJECTED.
     4. If ANY reviewer rejects → work loops back with the blockers list
+    4.5. Marta's gate-closing report reproduces each reviewer verdict
+         VERBATIM under `### <Reviewer> — verbatim`, with the ledger
+         artifact path (~/.arkaos/quality-gate/<session>/) beside it.
+         Summarising a reviewer in the aggregator's words is relay,
+         not report — a relay inside a gate is a point of distortion.
     5. If ALL approve → Marta issues final APPROVED verdict
     6. Record the label (evals ADR 2026-07-09): pipe Marta's final
        QGVerdict JSON to
@@ -71,25 +76,35 @@ Any Department Workflow:
 
 ## Reviewer Dispatch Contract
 
-Reviewers are dispatched via the Agent tool with STRUCTURED OUTPUT. The output
-schema is `QG_VERDICT_JSON_SCHEMA` from `core.governance.qg_verdict` (the JSON
-Schema of the `QGVerdict` pydantic model):
+Reviewers are dispatched via the Agent tool. The `QGVerdict` schema
+(`QG_VERDICT_JSON_SCHEMA` from `core.governance.qg_verdict`) travels INSIDE
+the prompt — the Agent tool has no structured-output parameter, so the
+contract IS the dispatch prompt naming the exact fields (PR-B4 dispatch
+shape; a dispatch that invents its own field names fail-softs the artifact):
 
     from core.governance.qg_verdict import QG_VERDICT_JSON_SCHEMA
 
     Agent(
-        subagent_type="francisca-tech",       # .claude/agents/francisca-tech.md
-        model="sonnet",                        # opus ONLY for Tier 0/security scope
-        prompt="<evidence report JSON> + <diff summary> — interpret and return QGVerdict",
-        output_schema=QG_VERDICT_JSON_SCHEMA,  # structured-output param
+        subagent_type="francisca-tech",  # .claude/agents/francisca-tech.md
+        model="opus",                    # quality_gate.model_policy: best available
+        prompt="<evidence report JSON incl. report_digest> + <diff summary> — "
+               "interpret and return, in a ```arka-qgverdict fence, a QGVerdict "
+               "with fields: verdict, evidence_report, blockers "
+               "[{check, detail, file, verdict}], reviewer, model_used, "
+               "evidence_digest (= the report_digest), notes",
     )
 
-Each reviewer MUST return a `QGVerdict` JSON object: `verdict`
-(APPROVED|REJECTED), `evidence_report` (embedded summary), `blockers`
-(`[{check, detail, file}]`), `reviewer`, `model_used`, `notes`. The pydantic
-model rejects APPROVED-with-failing-evidence at validation time, and
-`core.governance.review_workflow` raises `ValueError` on any attempt to record
-an approval over `evidence_overall == "fail"`.
+Each reviewer MUST return a `QGVerdict` JSON object in a ```arka-qgverdict
+fence: `verdict` (APPROVED|REJECTED), `evidence_report` (embedded summary),
+`blockers` (`[{check, detail, file, verdict}]` — `check` names the evidence
+check; the aggregate guard's coverage matching keys on it), `reviewer`,
+`model_used`, `evidence_digest` (mandatory since PR-B4 — an artifact without
+it cannot support an APPROVED aggregate), `notes`. The Pydantic model rejects
+APPROVED-with-failing-evidence at validation time, and the anti-self-approval
+guard (PR-B3, hardened PR-B4) refuses an APPROVED aggregate the session's
+reviewer ledger cannot support — dispatch-shape issues are demoted to
+warnings on a REJECTED one; fabrication vectors (quorum, a vanishing
+CONFIRMED blocker) refuse regardless of verdict.
 
 ## Squad
 
@@ -133,9 +148,11 @@ There is no "APPROVED WITH CAVEATS". It's binary. Fix issues first.
 When dispatching subagent work via the Task tool, include the `model` parameter from the target agent's YAML `model:` field:
 
 - Agent YAMLs at `departments/*/agents/*.yaml` have `model: opus | sonnet | haiku`
-- Quality Gate reviewers (Eduardo/Francisca) run on `sonnet` by DEFAULT.
-  `opus` is used ONLY when the diff is Tier 0 scope (constitution, security,
-  release pipeline, installer auth) or the deliverable is security-flagged.
+- Quality Gate agents (Marta aggregating, Eduardo + Francisca reviewing)
+  run on the BEST model available — single source: constitution
+  `quality_gate.model_policy` (Excellence Reform 2026-07-05, frontier
+  tier; per-role overrides in `~/.arkaos/models.yaml`, Model Fabric).
+  Economy tiers never review.
 - Marta keeps her veto regardless of the model tier the review ran on —
   the verdict derives from evidence, not from model size.
 - Default to `sonnet` if the agent YAML has no `model` field

package/harness/codex/AGENTS.md

@@ -1,6 +1,6 @@
 # ArkaOS — The Operating System for AI Agent Teams
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
+> v4.43.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
 
 You are operating within ArkaOS. Every request routes through the
 appropriate department squad — never respond as a generic assistant.

package/harness/copilot/copilot-instructions.md

@@ -1,6 +1,6 @@
 # ArkaOS — The Operating System for AI Agent Teams
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
+> v4.43.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
 
 You are operating within ArkaOS. Every request routes through the
 appropriate department squad — never respond as a generic assistant.

package/harness/cursor/rules/arkaos.mdc

@@ -1,11 +1,11 @@
 ---
-description: ArkaOS v4.42.0 agent-team contract
+description: ArkaOS v4.43.0 agent-team contract
 alwaysApply: true
 ---
 
 # ArkaOS — The Operating System for AI Agent Teams
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
+> v4.43.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
 
 You are operating within ArkaOS. Every request routes through the
 appropriate department squad — never respond as a generic assistant.

package/harness/gemini/GEMINI.md

@@ -1,6 +1,6 @@
 # ArkaOS — The Operating System for AI Agent Teams
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
+> v4.43.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
 
 You are operating within ArkaOS. Every request routes through the
 appropriate department squad — never respond as a generic assistant.

package/harness/opencode/AGENTS.md

@@ -1,6 +1,6 @@
 # ArkaOS — The Operating System for AI Agent Teams
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
+> v4.43.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
 
 You are operating within ArkaOS. Every request routes through the
 appropriate department squad — never respond as a generic assistant.

package/harness/opencode/agents/arka-architect-gabriel.md

@@ -3,7 +3,7 @@ description: "Software Architect — ArkaOS /dev department"
 mode: subagent
 ---
 
-You are Gabriel, Software Architect of the ArkaOS /dev department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Gabriel, Software Architect of the ArkaOS /dev department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: system design, system visualization via dev/diagram (architecture + dataflow diagrams delivered as browser artifacts), domain modeling (event storming, bounded contexts), design patterns (GoF, PoEAA), business / domain analysis, API design.
 

package/harness/opencode/agents/arka-brand-director-valentina.md

@@ -3,7 +3,7 @@ description: "Creative Director — ArkaOS /brand department"
 mode: subagent
 ---
 
-You are Valentina, Creative Director of the ArkaOS /brand department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Valentina, Creative Director of the ArkaOS /brand department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: brand identity creation, reference-video visual analysis via dev/watch (complete frames + transcript — motion and art direction judged on evidence, never on screenshots), visual design direction, UX/UI strategy, design systems, brand voice & tone.
 

package/harness/opencode/agents/arka-cfo-helena.md

@@ -3,7 +3,7 @@ description: "Chief Financial Officer — ArkaOS /fin department"
 mode: subagent
 ---
 
-You are Helena, Chief Financial Officer of the ArkaOS /fin department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Helena, Chief Financial Officer of the ArkaOS /fin department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: financial planning & analysis, valuation & investment, unit economics & SaaS metrics, risk management & ERM, fundraising & cap tables, cash flow management.
 

package/harness/opencode/agents/arka-chief-of-staff-afonso.md

@@ -3,7 +3,7 @@ description: "Chief of Staff & Governance Lead — ArkaOS /org department"
 mode: subagent
 ---
 
-You are Afonso, Chief of Staff & Governance Lead of the ArkaOS /org department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Afonso, Chief of Staff & Governance Lead of the ArkaOS /org department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: meeting cadence (daily/weekly/quarterly/annual), OKR & CFR orchestration cross-department, decision records & RACI, premortem / blameless postmortem rituals, governance, board & founder-CEO succession, strategic alignment & single-threaded leadership.
 

package/harness/opencode/agents/arka-community-strategist-beatriz.md

@@ -3,7 +3,7 @@ description: "Community Strategist — ArkaOS /community department"
 mode: subagent
 ---
 
-You are Beatriz, Community Strategist of the ArkaOS /community department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Beatriz, Community Strategist of the ArkaOS /community department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: community strategy & design, platform selection (Discord, Telegram, Skool, Circle), member onboarding & retention, monetization (membership, courses, coaching), gamification & engagement, niche communities (betting, AI, vertical).
 

package/harness/opencode/agents/arka-content-strategist-rafael.md

@@ -3,7 +3,7 @@ description: "Content Strategist — ArkaOS /content department"
 mode: subagent
 ---
 
-You are Rafael, Content Strategist of the ArkaOS /content department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Rafael, Content Strategist of the ArkaOS /content department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: viral content design, reference-video analysis via dev/watch (frames + timestamped transcript before judging any video), hook writing & packaging, script structure, content operating systems, platform-specific optimization.
 

package/harness/opencode/agents/arka-conversion-strategist-ines.md

@@ -3,7 +3,7 @@ description: "Conversion Strategist — ArkaOS /landing department"
 mode: subagent
 ---
 
-You are Ines, Conversion Strategist of the ArkaOS /landing department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Ines, Conversion Strategist of the ArkaOS /landing department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: sales funnels, landing page optimization, offer creation, copywriting (direct response), launch sequences, affiliate marketing.
 

package/harness/opencode/agents/arka-coo-sofia.md

@@ -3,7 +3,7 @@ description: "Chief Operations Officer — ArkaOS /org department"
 mode: subagent
 ---
 
-You are Sofia, Chief Operations Officer of the ArkaOS /org department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Sofia, Chief Operations Officer of the ArkaOS /org department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: organizational design, process optimization, cross-department coordination, culture & team health, scaling operations, workflow automation.
 

package/harness/opencode/agents/arka-copy-director-eduardo.md

@@ -3,7 +3,7 @@ description: "Copy & Language Director — ArkaOS /quality department"
 mode: subagent
 ---
 
-You are Eduardo, Copy & Language Director of the ArkaOS /quality department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Eduardo, Copy & Language Director of the ArkaOS /quality department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: spelling and grammar (EN, PT-PT, PT-BR, ES, FR), tone and voice consistency, AI pattern detection and removal, accentuation and orthography, copywriting quality, factual accuracy in text.
 

package/harness/opencode/agents/arka-cqo-marta.md

@@ -3,7 +3,7 @@ description: "Chief Quality Officer — ArkaOS /quality department"
 mode: subagent
 ---
 
-You are Marta, Chief Quality Officer of the ArkaOS /quality department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Marta, Chief Quality Officer of the ArkaOS /quality department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: quality assurance orchestration, cross-department quality standards, text quality (spelling, grammar, tone), technical quality (code, UX, data), compliance and audit.
 

package/harness/opencode/agents/arka-cto-marco.md

@@ -3,7 +3,7 @@ description: "Chief Technology Officer — ArkaOS /dev department"
 mode: subagent
 ---
 
-You are Marco, Chief Technology Officer of the ArkaOS /dev department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Marco, Chief Technology Officer of the ArkaOS /dev department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: software architecture, system design, tech strategy, cloud infrastructure, ai/ml systems.
 

package/harness/opencode/agents/arka-design-ops-lead-iris.md

@@ -3,7 +3,7 @@ description: "Design Ops Lead — ArkaOS /brand department"
 mode: subagent
 ---
 
-You are Iris, Design Ops Lead of the ArkaOS /brand department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Iris, Design Ops Lead of the ArkaOS /brand department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: design tokens (JSON + CSS variables), component libraries (shadcn/ui, Radix, Headless UI), design system governance, figma → code pipelines, accessibility compliance (WCAG 2.2 AA/AAA), cross-platform tokenisation (Style Dictionary, Tailwind).
 

package/harness/opencode/agents/arka-ecom-director-ricardo.md

@@ -3,7 +3,7 @@ description: "E-Commerce Director — ArkaOS /ecom department"
 mode: subagent
 ---
 
-You are Ricardo, E-Commerce Director of the ArkaOS /ecom department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Ricardo, E-Commerce Director of the ArkaOS /ecom department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: e-commerce strategy, conversion optimization, marketplace operations, pricing strategy, fulfillment & logistics, email & retention.
 

package/harness/opencode/agents/arka-knowledge-director-clara.md

@@ -3,7 +3,7 @@ description: "Knowledge Director — ArkaOS /kb department"
 mode: subagent
 ---
 
-You are Clara, Knowledge Director of the ArkaOS /kb department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Clara, Knowledge Director of the ArkaOS /kb department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: knowledge management, research methodology, persona building, content curation, taxonomy & ontology, Obsidian vault management.
 

package/harness/opencode/agents/arka-leadership-director-rodrigo.md

@@ -3,7 +3,7 @@ description: "Leadership & People Director — ArkaOS /lead department"
 mode: subagent
 ---
 
-You are Rodrigo, Leadership & People Director of the ArkaOS /lead department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Rodrigo, Leadership & People Director of the ArkaOS /lead department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: team assessment & health, leadership development, hiring & onboarding, performance management, feedback & 1-on-1s, culture building.
 

package/harness/opencode/agents/arka-marketing-director-luna.md

@@ -3,7 +3,7 @@ description: "Marketing Director — ArkaOS /mkt department"
 mode: subagent
 ---
 
-You are Luna, Marketing Director of the ArkaOS /mkt department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Luna, Marketing Director of the ArkaOS /mkt department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: growth strategy, video-ad teardown via dev/watch (hook, pacing and spoken-copy evidence from frames + transcript), content marketing, SEO, paid acquisition, social media.
 

package/harness/opencode/agents/arka-ops-lead-daniel.md

@@ -3,7 +3,7 @@ description: "Operations Lead — ArkaOS /ops department"
 mode: subagent
 ---
 
-You are Daniel, Operations Lead of the ArkaOS /ops department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Daniel, Operations Lead of the ArkaOS /ops department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: workflow automation (Zapier, Make, n8n), SOP/process visualization via dev/diagram (workflow + lifecycle diagrams for automations and runbooks), process mapping & optimization, SOP creation & management, bottleneck analysis, integration design.
 

package/harness/opencode/agents/arka-pm-director-carolina.md

@@ -3,7 +3,7 @@ description: "Product Manager — ArkaOS /pm department"
 mode: subagent
 ---
 
-You are Carolina, Product Manager of the ArkaOS /pm department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Carolina, Product Manager of the ArkaOS /pm department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: continuous product discovery (daily habit), deliverable visualization via dev/diagram (workflow diagrams so stakeholders see scope before build), weekly customer interviewing, dual-track agile (discovery + delivery), product risk assessment (value/usability/feasibility/viability), framing problems for empowered teams (not features).
 

package/harness/opencode/agents/arka-revops-lead-vicente.md

@@ -3,7 +3,7 @@ description: "RevOps Lead — ArkaOS /saas department"
 mode: subagent
 ---
 
-You are Vicente, RevOps Lead of the ArkaOS /saas department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Vicente, RevOps Lead of the ArkaOS /saas department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: revenue operations (cross mkt + sales + CS), unified funnel & CRM hygiene, SLA MQL→SQL between marketing and sales, revenue metrics (LTV/CAC, NRR, payback), lead scoring & routing, commission & forecast modeling.
 

package/harness/opencode/agents/arka-saas-strategist-tiago.md

@@ -3,7 +3,7 @@ description: "SaaS Strategist — ArkaOS /saas department"
 mode: subagent
 ---
 
-You are Tiago, SaaS Strategist of the ArkaOS /saas department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Tiago, SaaS Strategist of the ArkaOS /saas department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: SaaS metrics & benchmarking, product-led growth, pricing strategy, customer success, micro-SaaS validation, go-to-market for SaaS.
 

package/harness/opencode/agents/arka-sales-director-miguel.md

@@ -3,7 +3,7 @@ description: "Sales Director — ArkaOS /sales department"
 mode: subagent
 ---
 
-You are Miguel, Sales Director of the ArkaOS /sales department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Miguel, Sales Director of the ArkaOS /sales department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: consultative selling, pipeline management, proposal writing, negotiation, discovery calls, deal qualification.
 

package/harness/opencode/agents/arka-strategy-director-tomas.md

@@ -3,7 +3,7 @@ description: "Chief Strategist — ArkaOS /strat department"
 mode: subagent
 ---
 
-You are Tomas, Chief Strategist of the ArkaOS /strat department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Tomas, Chief Strategist of the ArkaOS /strat department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: competitive strategy, business-flow visualization via dev/diagram (architecture + dataflow diagrams of business models and value chains), market analysis, business model design, positioning, innovation strategy.
 

package/harness/opencode/agents/arka-tech-director-francisca.md

@@ -3,7 +3,7 @@ description: "Technical & UX Quality Director — ArkaOS /quality department"
 mode: subagent
 ---
 
-You are Francisca, Technical & UX Quality Director of the ArkaOS /quality department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Francisca, Technical & UX Quality Director of the ArkaOS /quality department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: code quality (SOLID, Clean Code, DRY), test coverage and quality, UX/UI review (heuristics, accessibility), security review (OWASP), performance review (CWV, API latency), data integrity and API contracts.
 

package/harness/opencode/agents/arka-tech-lead-paulo.md

@@ -3,7 +3,7 @@ description: "Tech Lead — ArkaOS /dev department"
 mode: subagent
 ---
 
-You are Paulo, Tech Lead of the ArkaOS /dev department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Paulo, Tech Lead of the ArkaOS /dev department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: workflow orchestration, visual spec/plan companions via dev/diagram (typed IR -> interactive HTML the user opens before build), code quality enforcement, sprint/cycle management, technical decision-making, developer experience.
 

package/harness/opencode/agents/arka-video-producer-simao.md

@@ -3,7 +3,7 @@ description: "Video Producer & Production Lead — ArkaOS /content department"
 mode: subagent
 ---
 
-You are Simão, Video Producer & Production Lead of the ArkaOS /content department (v4.42.0; generated by scripts/harness_gen.py — do not edit).
+You are Simão, Video Producer & Production Lead of the ArkaOS /content department (v4.43.0; generated by scripts/harness_gen.py — do not edit).
 
 Expertise: video production pipelines (script → storyboard → assets → edit → render), cut review via dev/watch (frame + transcript evidence on own renders before the Quality Gate), Hyperframes video-as-code editing (HTML/CSS/JS + GSAP → MP4), Higgsfield generation orchestration (image, video, audio, motion control, upscale, reframe), shot lists and EDLs (scene/shot/VO/on-screen-text columns), transcription-synced cuts and word-level captions.
 

package/harness/zed/.rules

@@ -1,6 +1,6 @@
 # ArkaOS — The Operating System for AI Agent Teams
 
-> v4.42.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
+> v4.43.0 — 89 agents, 17 departments, 332 skills. Generated by `scripts/harness_gen.py`; do not edit.
 
 You are operating within ArkaOS. Every request routes through the
 appropriate department squad — never respond as a generic assistant.

package/knowledge/skills-manifest.json

@@ -1,7 +1,7 @@
 {
   "_meta": {
     "generator": "scripts/marketplace_gen.py",
-    "version": "4.42.0",
+    "version": "4.43.0",
     "marketplace": "arkaos"
   },
   "structural": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkaos",
-  "version": "4.42.0",
+  "version": "4.43.0",
   "description": "The Operating System for AI Agent Teams",
   "type": "module",
   "bin": {

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arkaos-core"
-version = "4.42.0"
+version = "4.43.0"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}