[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GC342Z7GDSX752AM51YMD":3,"skill-same:01M73GC342Z7GDSX752AM51YMD":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M73GC342Z7GDSX752AM51YMD","decision-write-integrity",null,"Process guidance for designing and operating integrity gates around human decision writes — any governed record where a named human decision changes state: approvals, ticket transitions, ADR acceptances, waivers, sign-offs, state transitions. Covers the HARD BLOCK \u002F ACK \u002F DISPLAY enforcement taxonomy, off|shadow|enforce staged rollout, server-recomputed snapshot-hash propose-then-confirm flow (409 on stale), deterministic script-aware rationale substance checks, maker\u002Fchecker countersign with deny-by-default grants, and AI-recommendation divergence recording. Use when: designing or reviewing a decision-write gate, planning a gate rollout, hardening an approval path, or making human decisions auditable.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.agents\u002Fskills\u002Fdecision-write-integrity\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: decision-write-integrity\nversion: 1.0.0\ndescription: >\n  Process guidance for designing and operating integrity gates around human\n  decision writes — any governed record where a named human decision changes\n  state: approvals, ticket transitions, ADR acceptances, waivers, sign-offs,\n  state transitions. Covers the HARD BLOCK \u002F ACK \u002F DISPLAY enforcement\n  taxonomy, off|shadow|enforce staged rollout, server-recomputed\n  snapshot-hash propose-then-confirm flow (409 on stale), deterministic\n  script-aware rationale substance checks, maker\u002Fchecker countersign with\n  deny-by-default grants, and AI-recommendation divergence recording.\n  Use when: designing or reviewing a decision-write gate, planning a gate\n  rollout, hardening an approval path, or making human decisions auditable.\nstatus: active\nscope: common\nl2_propagate: false\nowner: pm\nlast_updated: 2026-10-28\nlast_reviewed: 2026-10-28\nprerequisites: []\nrelates_to:\n  - skill: meeting-facilitation\n    type: relates_to\nmetadata:\n  type: process\n  triggers:\n    - decision write integrity\n    - gate integrity\n    - approval gate\n    - hard block\n    - maker checker\n    - countersign\n    - snapshot hash\n    - decision audit\n---\n\n# decision-write-integrity\n\nProcess skill for designing and operating **integrity gates around human\ndecision writes** — any governed record where a named human decision changes\nstate: gate approvals, ticket transitions, ADR acceptances, waivers,\nsign-offs. Distilled from the gate-integrity pattern proven in\nProjects\u002Fco-newbiz (ADR-0186); domain-neutral by design.\n\nThe problem it solves: a decision-write path that records whatever a person\ntypes — unconditioned approvals, one-character rationales, self-approval,\nno second-person check, no record of what was known at decision time —\nproduces an audit trail that cannot be trusted or replayed.\n\n## Non-Negotiable Principles\n\n1. **The system never decides.** Gates make conflicts un-skippable and\n   permanent; they never choose the outcome or silently veto a human\n   decision. A stop decision (reject, hold, kill, withdraw) is never blocked\n   by any gate rule.\n2. **Hard block only what policy already binds, or what is mechanical\n   record hygiene.** Everything involving judgement about the substance\n   stays an acknowledgement.\n3. **The server recomputes.** The client never supplies compliance state;\n   it supplies acknowledgements plus the hash of what it saw.\n4. **Snapshot beside the decision.** What was known at decision time is\n   stored with the decision — append-only, immutable.\n5. **Write-time only.** No already-recorded decision is rewritten or\n   invalidated; legacy rows get a label, never a rewrite.\n\n## Enforcement Taxonomy\n\n| Class | Behavior | Use when | Examples |\n|---|---|---|---|\n| HARD BLOCK | write refused (HTTP 409\u002F422\u002F403) with a stable error code | a governing policy clause already makes the condition binding, or the check is mechanical hygiene with no judgement in it | missing prerequisite state; non-waivable item incomplete; mandatory numeric assumption never human-confirmed; same-person countersign |\n| ACK | write accepted only when the recorder explicitly acknowledges each listed item with a substantive reason | the signal involves judgement; the system must not decide, but the conflict must not be skippable | red risk grade; unassessed predicate; open non-waivable item |\n| DISPLAY | shown on the brief\u002Fpanel and stored in the snapshot; no input required | the fact should be visible but demands nothing | data-confidence cap; active waivers; inert rule count |\n\nRules:\n\n- ACK items carry stable keys (e.g. `predicate:\u003Cid>`); the server computes\n  the required set — a missing key returns 422 listing the keys, and extra\n  or unknown keys are rejected.\n- One acknowledgement reason may cover a group of related items, but one\n  record per item is stored.\n- Silence is never read as pass.\n\n## Staged Rollout (off | shadow | enforce)\n\nGate every rule family (rationale, snapshot\u002Fack, binding predicates,\nsequence ladder, maker\u002Fchecker, waivers, divergence) behind its own flag:\n\n| Mode | Behavior |\n|---|---|\n| off | rules dormant; unit-test default |\n| shadow | server computes and logs what it would block or require (`would_block:\u003Ccode>`, de-duplicated per entity, gate, code, day); production default |\n| enforce | rules bind |\n\nFlip discipline:\n\n- Production starts in shadow for every family; flip family by family.\n- Flip only after a soak window (e.g. 14 or more days in shadow, 10 or more\n  observed writes, zero unexplained would-block events), recorded per family\n  in a runbook.\n- Enforce order: mechanical hygiene first; rules that need a second\n  provisioned human (maker\u002Fchecker) last.\n- Rollback is setting the family to off. Schema stays additive — no\n  migration rollback is needed for behavior.\n\n## Propose-Then-Confirm Snapshot Flow\n\n1. **Propose** — agent or client submits the decision draft. The proposal\n   carries NO human-only fields (no snapshot hash, no acknowledgements);\n   the payload validator rejects them outright so no agent can\n   pre-acknowledge.\n2. **Confirm GET** — the human's confirm view requests a fresh snapshot.\n   The server recomputes all gate state (never trusts the client) and\n   returns the snapshot plus a `snapshot_hash` (SHA-256 over canonical\n   JSON: sorted keys, fixed number format, stable element ordering,\n   volatile fields excluded).\n3. **Confirm POST** — the human submits `snapshot_hash` plus\n   `acknowledgements[]`, each `{key, kind, reason}`.\n4. **Server verify** — recompute at write time; a changed hash returns\n   **409 snapshot_stale** with the fresh snapshot for re-review. Then\n   evaluate hard blocks in a defined order (first failure wins, all\n   failures listed), then the `ack_required` check.\n5. **Persist atomically** — snapshot, decision, acknowledgements,\n   dependent records, and the audit entry in one transaction. Snapshot\n   rows are append-only (no UPDATE\u002FDELETE path in code; a trigger forbids\n   both).\n6. **Every outcome snapshots** — not only approvals; a stop decision still\n   records what was known.\n\nThe snapshot stores, at minimum: binding-predicate outcomes (triggered \u002F\nunassessed \u002F passed, plus the inert count), risk-grade state and any\ndata-confidence cap, completeness-check state, confirmation state of\nmandatory numeric assumptions, active and expiring waivers, open tracked\nconditions, prerequisite\u002Fsequence state, and the AI recommendation.\n\n## Rationale Substance Checks\n\nDeterministic, script-aware, no model call. The check judges **form, not\nmerit** — whether the reasoning is good stays a human matter.\n\n- Normalize (Unicode NFKC, trim), then apply per profile:\n  - decision profile — minimum letter\u002Fdigit and token floors tuned per\n    dominant script (e.g. Latin: 20+ characters, 4+ words; Hangul: 12+\n    syllables, 3+ space-separated units); mixed text is judged by its\n    dominant script.\n  - acknowledgement profile — smaller floors (e.g. 12+ characters,\n    3+ tokens).\n- Reject: a placeholder denylist (case-folded, ending-normalized,\n  multilingual), repetitive runs (one character or syllable over 70\n  percent of letters), degenerate fragments, and rationales identical\n  (normalized) to another gate's rationale on the same entity.\n- Return stable reason codes (`too_short`, `placeholder`, `repetitive`,\n  ...); the UI renders localized catalog text; no hard-coded message\n  strings.\n- Existing rows are never re-checked or rewritten.\n\n## Maker\u002FChecker Countersign\n\nFor high-authority decisions (final approvals), the recorder (maker) cannot\napprove their own record:\n\n- State: `recorded` -> `pending_countersign` -> `effective`. A pending\n  countersign counts as NOT given for all downstream gating (sequence\n  ladder, closing, dependencies). Stop decisions take effect immediately —\n  no countersign is needed to stop.\n- The countersign comes from a different authenticated human holding the\n  matching reviewer role; same-person countersign is a 403.\n- A checker rejection leaves the maker's record non-effective and puts the\n  disagreement on the record (both rows retained); the maker may record a\n  new decision.\n- **Deny-by-default grants**: an absent or revoked grant means 403 on the\n  countersign\u002Fapprove\u002Fclear\u002Foverride routes only — it changes nothing\n  elsewhere. Grants are dated, revocable, admin-issued. Nobody grants\n  themselves a role, and agents, MCP calls, and bearer tokens never\n  exercise grants (cookie-session humans only).\n- Re-read the grant inside the write transaction — a revocation in flight\n  invalidates a pending countersign.\n\n## Waiver and Exception Hygiene\n\n- Approval is a separate authenticated act — never a free-text name in the\n  request body. Approver differs from requester and must hold the matching\n  role (403 otherwise).\n- Bounded duration (e.g. 90 days maximum from approval — hard-block a\n  longer expiry); no automatic extension; a renewal is a new request. A\n  waiver without a recorded approval timestamp never takes effect.\n- Non-waivable items refuse waiver requests outright (422).\n- Exceptions attached to a conditional approval become tracked objects\n  (condition precedent): text, owner role, clear-by milestone, status.\n  Clearing requires a different eligible person plus evidence. Open\n  conditions block the downstream stage they target.\n\n## AI-Recommendation Divergence Recording\n\n- Persist the AI recommendation (recommended decision, confidence,\n  generation reference) beside the human decision, with a link from the\n  decision to its brief.\n- If a recommendation exists and differs from the human decision, a\n  divergence reason meeting the decision rationale profile is required\n  (422 otherwise). If no brief was generated, store \"none\" and require\n  nothing.\n- The system never changes the human decision. Divergence counts feed\n  governance KPIs and base-rate learning — display only; no rate triggers\n  any block.\n\n## Design and Operate Checklists\n\nDesigning a gate:\n\n- [ ] Classify every rule HARD BLOCK \u002F ACK \u002F DISPLAY against principle 2\n- [ ] Stable error codes, defined evaluation order, all failures listed\n- [ ] Stop decisions never blocked; every outcome gets a snapshot\n- [ ] Flags per family; shadow before enforce; soak criteria written down\n- [ ] Grants deny-by-default; agents hold none; second human provisioned\n      before maker\u002Fchecker flips to enforce\n\nOperating a gate:\n\n- [ ] Weekly shadow report; zero unexplained would-blocks before any flip\n- [ ] KPIs: acknowledgement counts, unassessed share, divergence rate,\n      countersign latency, stale open conditions\n- [ ] Legacy rows labelled, never rewritten; audit events for every\n      control action (grant issue\u002Frevoke, countersign, override, clear)\n\n## Anti-Patterns\n\n- Hard-blocking judgement calls (risk grades, unassessed items) — the\n  system would decide.\n- Client-supplied compliance state — the recorder self-certifies.\n- LLM-judged rationale quality — unreproducible; a deterministic form\n  check is the gate rule, and model review stays decision support.\n- Silently averaging disagreement — checker rejection and AI divergence\n  stay on the record verbatim.\n- Bypasses for single-owner deployments — a bypass voids the control;\n  provision a second human instead.\n\n## Related Skills\n\n- `meeting-facilitation` — same philosophy one step upstream: synthesized\n  meeting outcomes are PROPOSALS for human approval, never decisions.\n\n## References (provenance)\n\nDistilled from the co-newbiz gate-integrity pattern (merged PR #743):\n\n- Projects\u002Fco-newbiz\u002Fdocs\u002Fadr\u002F0186-gate-integrity.md — enforcement classes\n  (D1), rationale check (D2), ladder (D7), maker\u002Fchecker (D6), divergence\n  (D9), owner decisions.\n- Projects\u002Fco-newbiz\u002Fdocs\u002Fdesigns\u002F2026-10-26-gate-integrity-design.md —\n  contracts (3.1-3.16), rollout (section 7), security (3.14).\n\nGeneralized here: the enforcement taxonomy, staged rollout, snapshot-hash\nflow, rationale profiles (per-script thresholds), grant model, and\ndivergence recording. Project-specific and intentionally NOT carried:\nindividual predicates, discount-rate semantics, track ladders, and policy\nclause numbering.\n","# decision-write-integrity\n\nProcess skill for designing and operating **integrity gates around human\ndecision writes** — any governed record where a named human decision changes\nstate: gate approvals, ticket transitions, ADR acceptances, waivers,\nsign-offs. Distilled from the gate-integrity pattern proven in\nProjects\u002Fco-newbiz (ADR-0186); domain-neutral by design.\n\nThe problem it solves: a decision-write path that records whatever a person\ntypes — unconditioned approvals, one-character rationales, self-approval,\nno second-person check, no record of what was known at decision time —\nproduces an audit trail that cannot be trusted or replayed.\n\n## Non-Negotiable Principles\n\n1. **The system never decides.** Gates make conflicts un-skippable and\n   permanent; they never choose the outcome or silently veto a human\n   decision. A stop decision (reject, hold, kill, withdraw) is never blocked\n   by any gate rule.\n2. **Hard block only what policy already binds, or what is mechanical\n   record hygiene.** Everything involving judgement about the substance\n   stays an acknowledgement.\n3. **The server recomputes.** The client never supplies compliance state;\n   it supplies acknowledgements plus the hash of what it saw.\n4. **Snapshot beside the decision.** What was known at decision time is\n   stored with the decision — append-only, immutable.\n5. **Write-time only.** No already-recorded decision is rewritten or\n   invalidated; legacy rows get a label, never a rewrite.\n\n## Enforcement Taxonomy\n\n| Class | Behavior | Use when | Examples |\n|---|---|---|---|\n| HARD BLOCK | write refused (HTTP 409\u002F422\u002F403) with a stable error code | a governing policy clause already makes the condition binding, or the check is mechanical hygiene with no judgement in it | missing prerequisite state; non-waivable item incomplete; mandatory numeric assumption never human-confirmed; same-person countersign |\n| ACK | write accepted only when the recorder explicitly acknowledges each listed item with a substantive reason | the signal involves judgement; the system must not decide, but the conflict must not be skippable | red risk grade; unassessed predicate; open non-waivable item |\n| DISPLAY | shown on the brief\u002Fpanel and stored in the snapshot; no input required | the fact should be visible but demands nothing | data-confidence cap; active waivers; inert rule count |\n\nRules:\n\n- ACK items carry stable keys (e.g. `predicate:\u003Cid>`); the server computes\n  the required set — a missing key returns 422 listing the keys, and extra\n  or unknown keys are rejected.\n- One acknowledgement reason may cover a group of related items, but one\n  record per item is stored.\n- Silence is never read as pass.\n\n## Staged Rollout (off | shadow | enforce)\n\nGate every rule family (rationale, snapshot\u002Fack, binding predicates,\nsequence ladder, maker\u002Fchecker, waivers, divergence) behind its own flag:\n\n| Mode | Behavior |\n|---|---|\n| off | rules dormant; unit-test default |\n| shadow | server computes and logs what it would block or require (`would_block:\u003Ccode>`, de-duplicated per entity, gate, code, day); production default |\n| enforce | rules bind |\n\nFlip discipline:\n\n- Production starts in shadow for every family; flip family by family.\n- Flip only after a soak window (e.g. 14 or more days in shadow, 10 or more\n  observed writes, zero unexplained would-block events), recorded per family\n  in a runbook.\n- Enforce order: mechanical hygiene first; rules that need a second\n  provisioned human (maker\u002Fchecker) last.\n- Rollback is setting the family to off. Schema stays additive — no\n  migration rollback is needed for behavior.\n\n## Propose-Then-Confirm Snapshot Flow\n\n1. **Propose** — agent or client submits the decision draft. The proposal\n   carries NO human-only fields (no snapshot hash, no acknowledgements);\n   the payload validator rejects them outright so no agent can\n   pre-acknowledge.\n2. **Confirm GET** — the human's confirm view requests a fresh snapshot.\n   The server recomputes all gate state (never trusts the client) and\n   returns the snapshot plus a `snapshot_hash` (SHA-256 over canonical\n   JSON: sorted keys, fixed number format, stable element ordering,\n   volatile fields excluded).\n3. **Confirm POST** — the human submits `snapshot_hash` plus\n   `acknowledgements[]`, each `{key, kind, reason}`.\n4. **Server verify** — recompute at write time; a changed hash returns\n   **409 snapshot_stale** with the fresh snapshot for re-review. Then\n   evaluate hard blocks in a defined order (first failure wins, all\n   failures listed), then the `ack_required` check.\n5. **Persist atomically** — snapshot, decision, acknowledgements,\n   dependent records, and the audit entry in one transaction. Snapshot\n   rows are append-only (no UPDATE\u002FDELETE path in code; a trigger forbids\n   both).\n6. **Every outcome snapshots** — not only approvals; a stop decision still\n   records what was known.\n\nThe snapshot stores, at minimum: binding-predicate outcomes (triggered \u002F\nunassessed \u002F passed, plus the inert count), risk-grade state and any\ndata-confidence cap, completeness-check state, confirmation state of\nmandatory numeric assumptions, active and expiring waivers, open tracked\nconditions, prerequisite\u002Fsequence state, and the AI recommendation.\n\n## Rationale Substance Checks\n\nDeterministic, script-aware, no model call. The check judges **form, not\nmerit** — whether the reasoning is good stays a human matter.\n\n- Normalize (Unicode NFKC, trim), then apply per profile:\n  - decision profile — minimum letter\u002Fdigit and token floors tuned per\n    dominant script (e.g. Latin: 20+ characters, 4+ words; Hangul: 12+\n    syllables, 3+ space-separated units); mixed text is judged by its\n    dominant script.\n  - acknowledgement profile — smaller floors (e.g. 12+ characters,\n    3+ tokens).\n- Reject: a placeholder denylist (case-folded, ending-normalized,\n  multilingual), repetitive runs (one character or syllable over 70\n  percent of letters), degenerate fragments, and rationales identical\n  (normalized) to another gate's rationale on the same entity.\n- Return stable reason codes (`too_short`, `placeholder`, `repetitive`,\n  ...); the UI renders localized catalog text; no hard-coded message\n  strings.\n- Existing rows are never re-checked or rewritten.\n\n## Maker\u002FChecker Countersign\n\nFor high-authority decisions (final approvals), the recorder (maker) cannot\napprove their own record:\n\n- State: `recorded` -> `pending_countersign` -> `effective`. A pending\n  countersign counts as NOT given for all downstream gating (sequence\n  ladder, closing, dependencies). Stop decisions take effect immediately —\n  no countersign is needed to stop.\n- The countersign comes from a different authenticated human holding the\n  matching reviewer role; same-person countersign is a 403.\n- A checker rejection leaves the maker's record non-effective and puts the\n  disagreement on the record (both rows retained); the maker may record a\n  new decision.\n- **Deny-by-default grants**: an absent or revoked grant means 403 on the\n  countersign\u002Fapprove\u002Fclear\u002Foverride routes only — it changes nothing\n  elsewhere. Grants are dated, revocable, admin-issued. Nobody grants\n  themselves a role, and agents, MCP calls, and bearer tokens never\n  exercise grants (cookie-session humans only).\n- Re-read the grant inside the write transaction — a revocation in flight\n  invalidates a pending countersign.\n\n## Waiver and Exception Hygiene\n\n- Approval is a separate authenticated act — never a free-text name in the\n  request body. Approver differs from requester and must hold the matching\n  role (403 otherwise).\n- Bounded duration (e.g. 90 days maximum from approval — hard-block a\n  longer expiry); no automatic extension; a renewal is a new request. A\n  waiver without a recorded approval timestamp never takes effect.\n- Non-waivable items refuse waiver requests outright (422).\n- Exceptions attached to a conditional approval become tracked objects\n  (condition precedent): text, owner role, clear-by milestone, status.\n  Clearing requires a different eligible person plus evidence. Open\n  conditions block the downstream stage they target.\n\n## AI-Recommendation Divergence Recording\n\n- Persist the AI recommendation (recommended decision, confidence,\n  generation reference) beside the human decision, with a link from the\n  decision to its brief.\n- If a recommendation exists and differs from the human decision, a\n  divergence reason meeting the decision rationale profile is required\n  (422 otherwise). If no brief was generated, store \"none\" and require\n  nothing.\n- The system never changes the human decision. Divergence counts feed\n  governance KPIs and base-rate learning — display only; no rate triggers\n  any block.\n\n## Design and Operate Checklists\n\nDesigning a gate:\n\n- [ ] Classify every rule HARD BLOCK \u002F ACK \u002F DISPLAY against principle 2\n- [ ] Stable error codes, defined evaluation order, all failures listed\n- [ ] Stop decisions never blocked; every outcome gets a snapshot\n- [ ] Flags per family; shadow before enforce; soak criteria written down\n- [ ] Grants deny-by-default; agents hold none; second human provisioned\n      before maker\u002Fchecker flips to enforce\n\nOperating a gate:\n\n- [ ] Weekly shadow report; zero unexplained would-blocks before any flip\n- [ ] KPIs: acknowledgement counts, unassessed share, divergence rate,\n      countersign latency, stale open conditions\n- [ ] Legacy rows labelled, never rewritten; audit events for every\n      control action (grant issue\u002Frevoke, countersign, override, clear)\n\n## Anti-Patterns\n\n- Hard-blocking judgement calls (risk grades, unassessed items) — the\n  system would decide.\n- Client-supplied compliance state — the recorder self-certifies.\n- LLM-judged rationale quality — unreproducible; a deterministic form\n  check is the gate rule, and model review stays decision support.\n- Silently averaging disagreement — checker rejection and AI divergence\n  stay on the record verbatim.\n- Bypasses for single-owner deployments — a bypass voids the control;\n  provision a second human instead.\n\n## Related Skills\n\n- `meeting-facilitation` — same philosophy one step upstream: synthesized\n  meeting outcomes are PROPOSALS for human approval, never decisions.\n\n## References (provenance)\n\nDistilled from the co-newbiz gate-integrity pattern (merged PR #743):\n\n- Projects\u002Fco-newbiz\u002Fdocs\u002Fadr\u002F0186-gate-integrity.md — enforcement classes\n  (D1), rationale check (D2), ladder (D7), maker\u002Fchecker (D6), divergence\n  (D9), owner decisions.\n- Projects\u002Fco-newbiz\u002Fdocs\u002Fdesigns\u002F2026-10-26-gate-integrity-design.md —\n  contracts (3.1-3.16), rollout (section 7), security (3.14).\n\nGeneralized here: the enforcement taxonomy, staged rollout, snapshot-hash\nflow, rationale profiles (per-script thresholds), grant model, and\ndivergence recording. Project-specific and intentionally NOT carried:\nindividual predicates, discount-rate semantics, track ladders, and policy\nclause numbering.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":38,"description":42,"l2_propagate":19,"last_updated":43,"last_reviewed":43,"prerequisites":44},"pm","common","active","1.0.0",{"type":28,"triggers":29},"process",[30,31,32,33,34,35,36,37],"decision write integrity","gate integrity","approval gate","hard block","maker checker","countersign","snapshot hash","decision audit",[39],{"type":40,"skill":41},"relates_to","meeting-facilitation","Process guidance for designing and operating integrity gates around human decision writes — any governed record where a named human decision changes state: approvals, ticket transitions, ADR acceptances, waivers, sign-offs, state transitions. Covers the HARD BLOCK \u002F ACK \u002F DISPLAY enforcement taxonomy, off|shadow|enforce staged rollout, server-recomputed snapshot-hash propose-then-confirm flow (409 on stale), deterministic script-aware rationale substance checks, maker\u002Fchecker countersign with deny-by-default grants, and AI-recommendation divergence recording. Use when: designing or reviewing a decision-write gate, planning a gate rollout, hardening an approval path, or making human decisions auditable.\n",1793145600000,[],"main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fcommon\u002F.agents\u002Fskills\u002Fdecision-write-integrity",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill decision-write-integrity",{"tool":59,"command":60},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill decision-write-integrity",{"tool":62,"command":63},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill decision-write-integrity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.agents\u002Fskills\u002Fdecision-write-integrity\u002FSKILL.md",true,[],[68,76,81,86,91,96],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":77,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":75},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":82,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":75},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":87,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":75},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":92,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":75},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":97,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":75},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]