[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AJRYXBW8885TMS7FSJY8BB":3,"skill-same:01M7AJRYXBW8885TMS7FSJY8BB":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AJRYXBW8885TMS7FSJY8BB","vibey-domain-model",null,"Phases, jobs, ledger, handoff, rotation, and the no-loss gate — the core domain types and invariants in vibey.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002F.claude\u002Fskills\u002Fvibey-domain-model\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vibey-domain-model\ndescription: Phases, jobs, ledger, handoff, rotation, and the no-loss gate — the core domain types and invariants in vibey.\nallowed-tools: Read\n---\n\n# vibey domain model\n\nRead `docs\u002Fplans\u002Fdomain-model.md` before touching `domain\u002F`. This skill is a\ncompressed orientation; the full spec lives in that doc.\n\n## Phases\n\nSix numbered phases plus optional visual interstitial:\n\n```\nINTAKE → ① DESIGN → [optional VISUAL_DESIGN] → ② BUILD ⇄ ③ REVIEW\n         ▲──────────────────────────┘               │\n                                                     │\n③ ── user declines deployment ──────────────────────→ DONE (local)\n  │ user opts into deployment\n  ▼\n④ DEPLOY_DESIGN → ⑤ DEPLOY_EXECUTE → ⑥ DEPLOY_REVIEW → DONE (deployed)\n```\n\nInteractive phases (talk to the user): ①, ③, ④, ⑥, VISUAL_DESIGN.\nAutonomous phases (unattended): ②, ⑤.\n\n**Loop-backs:**\n- `BUILD → DESIGN` when blocked on ambiguity (spec insufficient).\n- `REVIEW → DESIGN` (default) or `REVIEW → BUILD` (fast path when every\n  finding is `unambiguous`). See ADR-0010.\n- `DEPLOY_REVIEW` can route to ④, ⑤, or back to ①\u002F②\u002F③ depending on the\n  failure classification.\n\n**Opt-in gates:**\n- Visual design: after ① accepts a buildable spec, vibey asks whether to\n  enter the visual-design interstitial. Declining takes the `DESIGN → BUILD`\n  edge directly.\n- Deployment: after ③ has no open product findings, vibey asks whether to\n  work on deployment. Declining records `completion_mode = \"local\"` and\n  transitions to `DONE` without enqueueing any Azure job.\n\nSee ADR-0014 (optional visual-design and deployment opt-in).\n\n## Jobs\n\nJob kinds are strings registered against handlers in `bootstrap.py` (25 kinds\nas of 2026-09-15):\n- DESIGN: `design.interview`, `design.research`, `design.synthesize`, `design.spec`\n- VISUAL_DESIGN: `visual.inventory`, `visual.plan`\n- BUILD: `build.decompose` (alias `build.plan`), `build.implement`, `build.verify`,\n  `build.integrate`\n- REVIEW: `review.demo`, `review.collect`, `review.triage`, `review.deployment_choice`\n- DEPLOY_DESIGN: `deploy.design`, `deploy.interview`, `deploy.synthesize`,\n  `deploy.spec` (alias `deploy.accept`)\n- DEPLOY_EXECUTE: `deploy.execute` (alias `deploy.graph`)\n- DEPLOY_REVIEW: `deploy.demo`, `deploy.triage`, `deploy.route`\n\n`docs\u002Fplans\u002Fphase-protocols.md` also names kinds that are not registered\n(`media.generate.*`, `visual.review`, `deploy.discover`\u002F`plan`\u002F`validate`\u002F`apply`\u002F\n`release`\u002F`verify`\u002F`recover`\u002F`collect`); treat those as planned. Handoff is not a\njob kind: it runs inside the engine-driven job through `application\u002Fwind_down.py`\nand `application\u002Fhandoff_orchestration.py`.\n\n**Job lifecycle (`domain\u002Fjob.py::JobState`):**\n`ready → leased → succeeded | failed | awaiting_human | awaiting_capacity | cancelled`.\n\n**Failure classes (`domain\u002Fjob.py::FailureClass`):** `capacity` (opens the\ncircuit), `engine` (opens after 3), `work` (the code is wrong; circuit untouched),\n`vibey` (our bug; circuit untouched).\n\n**Bounded ladders park, they do not loop.** When `build.implement` or\n`build.verify` exhausts its effort ladder (or a spend cap), the job parks behind a\nhuman gate. The answer can grant a bound (`max_attempts` for implement attempts,\n`max_rounds` for verify repair rounds, `max_dollars`\u002F`max_turns` for spend);\nfurther attempts run at the ladder's top effort until that grant is used up, then\npark again (ADR-0024; `granted_limit`\u002F`granted_amount` in\n`application\u002Fbuild_verify_handler.py`).\n\n**Idempotency:** every job is idempotent under replay via `idempotency_key` —\na deterministic hash of `(project_id, cycle, kind, subject)`. Re-enqueueing\nthe same logical work is a no-op. Handlers also guard their own side effects.\n\n**Parallel vs serial:** some jobs run in parallel (e.g., `build.implement` —\neach work item in its own git worktree). Others are serial (e.g.,\n`build.integrate` — one integration branch, serialised per project and cycle by a\nPostgres advisory lock in `infrastructure\u002Fdb\u002Fadvisory_lock.py`, ADR-0029).\n\nSee `domain\u002Fjob.py` (`JobState`, `FailureClass`, `backoff()`,\n`idempotency_key()`) and the handlers in `application\u002F*_handler.py`.\n\n## Ledger\n\nThe **append-only event log** in Postgres, written in a vendor-neutral schema.\nVendor transcripts (`~\u002F.claude\u002Fprojects\u002F**\u002F*.jsonl`, codex rollouts) are\ncopied in as *attachments* referenced by events — they are\nevidence, not state.\n\n**Event kinds (26 total, `domain\u002Fledger.py::EventKind`):** `SessionSeeded`,\n`TurnRequested`, `TurnCompleted`, `ToolInvoked`, `TranscriptRecorded`, `FileEdited`,\n`VerdictRendered`,\n`CapacityRejected`, `QuestionAsked`, `AnswerGiven`, `DecisionRecorded`,\n`AssumptionStated`, `FindingRaised`, `FindingResolved`, `ArtifactProduced`,\n`SavePointCreated`, `HandoffInitiated`, `HandoffAccepted`, `PhaseTransitioned`,\n`BudgetSpent`, and the ADR-0014 opt-in gate events `VisualDesignOptedIn`,\n`VisualDesignDeclined`, `VisualDesignAccepted`, `VisualDesignWaived`,\n`DeploymentOptedIn`, `DeploymentDeclined`.\n\n**Readers are forward compatible, writers strict (vibey#275):** a stored kind this vibey does not know is read as `UnrecognizedEventKind` (so `LedgerEvent.kind` is `EventKind | UnrecognizedEventKind`), kept in every range, full ledger and digest, skipped by every projection, and never written. Match kinds with `is EventKind.X` and narrow with `isinstance(kind, EventKind)` before using a member-only attribute.\n\n**Closable events:** `QuestionAsked`, `DecisionRecorded`, `AssumptionStated`,\n`FindingRaised` — these are the events the no-loss gate checks.\n\n**Digest:** every event carries a `digest` (SHA-256 of canonical JSON payload).\n`digest_range()` computes an order-sensitive Merkle-ish fold of a sequence of\nevents — this is what R6 (range integrity) checks.\n\nSee `domain\u002Fledger.py` and `docs\u002Fplans\u002Fhandoff-protocol.md`.\n\n## Handoff and the no-loss gate\n\nWhen an engine hits `CreditsExhausted`, vibey:\n1. Produces a `HandoffBrief` (the outgoing engine writes it, or the incoming\n   engine synthesizes it if the outgoing is dead).\n2. Verifies it against the **no-loss gate** (`domain\u002Fnoloss.py::verify()`).\n3. If the gate passes, writes the full ledger to\n   `\u003Cworktree>\u002F.vibey\u002Fhandoff\u002Fledger.jsonl` and seeds the next engine.\n4. If the gate fails, regenerates (up to 3 attempts), then escalates to\n   `full_transcript` mode, then raises a human gate. In that mode the gate waives\n   R1–R5, R7, R9; the design inlines the whole range, but as built the range is only\n   the `ledger.jsonl` file named in the seed prompt — do not describe it as inlined.\n\n**The 10 rules (R1–R10):**\n- R1: remaining-work closure\n- R2: open-question closure\n- R3: decision closure\n- R4: assumption closure\n- R5: finding closure\n- R6: range integrity (digest match)\n- R7: artifact closure\n- R8: budget carry\n- R9: constraint closure\n- R10: containment (nothing in the brief contradicts the spec)\n\nThe gate is **pure and deterministic** — no model call. This is the reason\nrotation is safe.\n\nSee ADR-0004 (no-loss gate on handoff) and `domain\u002Fnoloss.py`.\n\n## Rotation\n\n**Smooth weighted round robin** (nginx-style SWRR), not naive modulo. Engines\nare selected from the eligible set via `domain\u002Frotation.py::select()`.\n\n**Eligibility:** installed, authenticated (`doctor` passed within TTL),\ncircuit not `open`, capability requirements met, and per-phase allow-list\npermits it.\n\n**When rotation happens:** at boundaries only — never mid-turn. Triggers:\nnew work item starts, capacity rejection (forced, exclude the rejecting\nengine), effort escalation, phase transition, operator-requested handoff.\n\n**Properties (property-tested):**\n- No starvation: over `sum(effective_weight)` consecutive selections, every\n  candidate with `effective_weight > 0` is selected at least once.\n- Weight fidelity: selection counts converge to weight ratios within ±1 over\n  any full period.\n- Smoothness: no candidate is selected twice consecutively while another with\n  `effective_weight > 0` has gone unselected longer.\n- Determinism: identical candidate state produces an identical selection.\n\n**Wiring:** `application\u002Fengine_selector.py::EngineSelector` calls `select()`\nfor engine-driven BUILD jobs, through `SelectingEngineProvider` in `bootstrap.py`.\nCandidates come from `engine_health` rows, so an engine without a recorded\n`vibey doctor --conformance --record` pass is never eligible. A local engine joins\nonly while its switch is on — gptossloop unless switched off, qwenloop and\nclaudeloop-local only when switched on — and is preferred first (ADR-0038,\nADR-0064).\n\nSee ADR-0005 (smooth weighted round robin), ADR-0007 (rotate at boundaries),\nand `domain\u002Frotation.py`.\n\n## Effort ladder\n\nVibey speaks a normalized 5-level ladder: `TRIVIAL, LOW, STANDARD, HIGH, MAX`.\nEach engine descriptor provides a **projection** onto native flags, which may\nsaturate.\n\n**Phase base effort:**\n- ① DESIGN: `HIGH`\n- VISUAL_DESIGN: `HIGH`\n- ② BUILD: `LOW` (auto-escalating to `STANDARD` → `HIGH` after failures)\n- ③ REVIEW: `HIGH`\n- ④ DEPLOY_DESIGN: `HIGH`\n- ⑤ DEPLOY_EXECUTE: `LOW` (auto-escalating)\n- ⑥ DEPLOY_REVIEW: `HIGH`\n\n`Phase` also carries `DEPLOY` (a legacy single-phase bridge, base `LOW`) and\n`ABANDONED`; the phase diagram omits them deliberately.\n\nSee ADR-0006 (normalized effort ladder) and `domain\u002Feffort.py`.\n\n## Capacity states\n\n`Available | WindowExhausted | CreditsExhausted | AuthenticationFailed`\n\n**The one rule that matters:**\n`CreditsExhausted` has **no `resets_at` field** and can never acquire one.\nThis is enforced at three independent layers:\n1. Type-level: `domain\u002Fcapacity.py`'s dataclass has no such attribute.\n2. Property-tested: `schedule_probe(CreditsExhausted(...))` can only return a\n   `BackoffProbe`, never a `DeadlineProbe`.\n3. Database-level: the `engine_health` table has a CHECK constraint\n   `credits_never_have_a_deadline` that rejects any `INSERT`\u002F`UPDATE` with\n   `capacity_state = 'CreditsExhausted'` and non-null `resets_at`.\n\nSee `domain\u002Fcapacity.py`, `domain\u002Fcircuit.py`, the constraint in\n`migrations\u002F0007_engine_health_rotation.sql`, and the CLAUDE.md non-negotiable \"A\ncapacity rejection always outranks a completion claim\" (it has no ADR of its\nown).\n","# vibey domain model\n\nRead `docs\u002Fplans\u002Fdomain-model.md` before touching `domain\u002F`. This skill is a\ncompressed orientation; the full spec lives in that doc.\n\n## Phases\n\nSix numbered phases plus optional visual interstitial:\n\n```\nINTAKE → ① DESIGN → [optional VISUAL_DESIGN] → ② BUILD ⇄ ③ REVIEW\n         ▲──────────────────────────┘               │\n                                                     │\n③ ── user declines deployment ──────────────────────→ DONE (local)\n  │ user opts into deployment\n  ▼\n④ DEPLOY_DESIGN → ⑤ DEPLOY_EXECUTE → ⑥ DEPLOY_REVIEW → DONE (deployed)\n```\n\nInteractive phases (talk to the user): ①, ③, ④, ⑥, VISUAL_DESIGN.\nAutonomous phases (unattended): ②, ⑤.\n\n**Loop-backs:**\n- `BUILD → DESIGN` when blocked on ambiguity (spec insufficient).\n- `REVIEW → DESIGN` (default) or `REVIEW → BUILD` (fast path when every\n  finding is `unambiguous`). See ADR-0010.\n- `DEPLOY_REVIEW` can route to ④, ⑤, or back to ①\u002F②\u002F③ depending on the\n  failure classification.\n\n**Opt-in gates:**\n- Visual design: after ① accepts a buildable spec, vibey asks whether to\n  enter the visual-design interstitial. Declining takes the `DESIGN → BUILD`\n  edge directly.\n- Deployment: after ③ has no open product findings, vibey asks whether to\n  work on deployment. Declining records `completion_mode = \"local\"` and\n  transitions to `DONE` without enqueueing any Azure job.\n\nSee ADR-0014 (optional visual-design and deployment opt-in).\n\n## Jobs\n\nJob kinds are strings registered against handlers in `bootstrap.py` (25 kinds\nas of 2026-09-15):\n- DESIGN: `design.interview`, `design.research`, `design.synthesize`, `design.spec`\n- VISUAL_DESIGN: `visual.inventory`, `visual.plan`\n- BUILD: `build.decompose` (alias `build.plan`), `build.implement`, `build.verify`,\n  `build.integrate`\n- REVIEW: `review.demo`, `review.collect`, `review.triage`, `review.deployment_choice`\n- DEPLOY_DESIGN: `deploy.design`, `deploy.interview`, `deploy.synthesize`,\n  `deploy.spec` (alias `deploy.accept`)\n- DEPLOY_EXECUTE: `deploy.execute` (alias `deploy.graph`)\n- DEPLOY_REVIEW: `deploy.demo`, `deploy.triage`, `deploy.route`\n\n`docs\u002Fplans\u002Fphase-protocols.md` also names kinds that are not registered\n(`media.generate.*`, `visual.review`, `deploy.discover`\u002F`plan`\u002F`validate`\u002F`apply`\u002F\n`release`\u002F`verify`\u002F`recover`\u002F`collect`); treat those as planned. Handoff is not a\njob kind: it runs inside the engine-driven job through `application\u002Fwind_down.py`\nand `application\u002Fhandoff_orchestration.py`.\n\n**Job lifecycle (`domain\u002Fjob.py::JobState`):**\n`ready → leased → succeeded | failed | awaiting_human | awaiting_capacity | cancelled`.\n\n**Failure classes (`domain\u002Fjob.py::FailureClass`):** `capacity` (opens the\ncircuit), `engine` (opens after 3), `work` (the code is wrong; circuit untouched),\n`vibey` (our bug; circuit untouched).\n\n**Bounded ladders park, they do not loop.** When `build.implement` or\n`build.verify` exhausts its effort ladder (or a spend cap), the job parks behind a\nhuman gate. The answer can grant a bound (`max_attempts` for implement attempts,\n`max_rounds` for verify repair rounds, `max_dollars`\u002F`max_turns` for spend);\nfurther attempts run at the ladder's top effort until that grant is used up, then\npark again (ADR-0024; `granted_limit`\u002F`granted_amount` in\n`application\u002Fbuild_verify_handler.py`).\n\n**Idempotency:** every job is idempotent under replay via `idempotency_key` —\na deterministic hash of `(project_id, cycle, kind, subject)`. Re-enqueueing\nthe same logical work is a no-op. Handlers also guard their own side effects.\n\n**Parallel vs serial:** some jobs run in parallel (e.g., `build.implement` —\neach work item in its own git worktree). Others are serial (e.g.,\n`build.integrate` — one integration branch, serialised per project and cycle by a\nPostgres advisory lock in `infrastructure\u002Fdb\u002Fadvisory_lock.py`, ADR-0029).\n\nSee `domain\u002Fjob.py` (`JobState`, `FailureClass`, `backoff()`,\n`idempotency_key()`) and the handlers in `application\u002F*_handler.py`.\n\n## Ledger\n\nThe **append-only event log** in Postgres, written in a vendor-neutral schema.\nVendor transcripts (`~\u002F.claude\u002Fprojects\u002F**\u002F*.jsonl`, codex rollouts) are\ncopied in as *attachments* referenced by events — they are\nevidence, not state.\n\n**Event kinds (26 total, `domain\u002Fledger.py::EventKind`):** `SessionSeeded`,\n`TurnRequested`, `TurnCompleted`, `ToolInvoked`, `TranscriptRecorded`, `FileEdited`,\n`VerdictRendered`,\n`CapacityRejected`, `QuestionAsked`, `AnswerGiven`, `DecisionRecorded`,\n`AssumptionStated`, `FindingRaised`, `FindingResolved`, `ArtifactProduced`,\n`SavePointCreated`, `HandoffInitiated`, `HandoffAccepted`, `PhaseTransitioned`,\n`BudgetSpent`, and the ADR-0014 opt-in gate events `VisualDesignOptedIn`,\n`VisualDesignDeclined`, `VisualDesignAccepted`, `VisualDesignWaived`,\n`DeploymentOptedIn`, `DeploymentDeclined`.\n\n**Readers are forward compatible, writers strict (vibey#275):** a stored kind this vibey does not know is read as `UnrecognizedEventKind` (so `LedgerEvent.kind` is `EventKind | UnrecognizedEventKind`), kept in every range, full ledger and digest, skipped by every projection, and never written. Match kinds with `is EventKind.X` and narrow with `isinstance(kind, EventKind)` before using a member-only attribute.\n\n**Closable events:** `QuestionAsked`, `DecisionRecorded`, `AssumptionStated`,\n`FindingRaised` — these are the events the no-loss gate checks.\n\n**Digest:** every event carries a `digest` (SHA-256 of canonical JSON payload).\n`digest_range()` computes an order-sensitive Merkle-ish fold of a sequence of\nevents — this is what R6 (range integrity) checks.\n\nSee `domain\u002Fledger.py` and `docs\u002Fplans\u002Fhandoff-protocol.md`.\n\n## Handoff and the no-loss gate\n\nWhen an engine hits `CreditsExhausted`, vibey:\n1. Produces a `HandoffBrief` (the outgoing engine writes it, or the incoming\n   engine synthesizes it if the outgoing is dead).\n2. Verifies it against the **no-loss gate** (`domain\u002Fnoloss.py::verify()`).\n3. If the gate passes, writes the full ledger to\n   `\u003Cworktree>\u002F.vibey\u002Fhandoff\u002Fledger.jsonl` and seeds the next engine.\n4. If the gate fails, regenerates (up to 3 attempts), then escalates to\n   `full_transcript` mode, then raises a human gate. In that mode the gate waives\n   R1–R5, R7, R9; the design inlines the whole range, but as built the range is only\n   the `ledger.jsonl` file named in the seed prompt — do not describe it as inlined.\n\n**The 10 rules (R1–R10):**\n- R1: remaining-work closure\n- R2: open-question closure\n- R3: decision closure\n- R4: assumption closure\n- R5: finding closure\n- R6: range integrity (digest match)\n- R7: artifact closure\n- R8: budget carry\n- R9: constraint closure\n- R10: containment (nothing in the brief contradicts the spec)\n\nThe gate is **pure and deterministic** — no model call. This is the reason\nrotation is safe.\n\nSee ADR-0004 (no-loss gate on handoff) and `domain\u002Fnoloss.py`.\n\n## Rotation\n\n**Smooth weighted round robin** (nginx-style SWRR), not naive modulo. Engines\nare selected from the eligible set via `domain\u002Frotation.py::select()`.\n\n**Eligibility:** installed, authenticated (`doctor` passed within TTL),\ncircuit not `open`, capability requirements met, and per-phase allow-list\npermits it.\n\n**When rotation happens:** at boundaries only — never mid-turn. Triggers:\nnew work item starts, capacity rejection (forced, exclude the rejecting\nengine), effort escalation, phase transition, operator-requested handoff.\n\n**Properties (property-tested):**\n- No starvation: over `sum(effective_weight)` consecutive selections, every\n  candidate with `effective_weight > 0` is selected at least once.\n- Weight fidelity: selection counts converge to weight ratios within ±1 over\n  any full period.\n- Smoothness: no candidate is selected twice consecutively while another with\n  `effective_weight > 0` has gone unselected longer.\n- Determinism: identical candidate state produces an identical selection.\n\n**Wiring:** `application\u002Fengine_selector.py::EngineSelector` calls `select()`\nfor engine-driven BUILD jobs, through `SelectingEngineProvider` in `bootstrap.py`.\nCandidates come from `engine_health` rows, so an engine without a recorded\n`vibey doctor --conformance --record` pass is never eligible. A local engine joins\nonly while its switch is on — gptossloop unless switched off, qwenloop and\nclaudeloop-local only when switched on — and is preferred first (ADR-0038,\nADR-0064).\n\nSee ADR-0005 (smooth weighted round robin), ADR-0007 (rotate at boundaries),\nand `domain\u002Frotation.py`.\n\n## Effort ladder\n\nVibey speaks a normalized 5-level ladder: `TRIVIAL, LOW, STANDARD, HIGH, MAX`.\nEach engine descriptor provides a **projection** onto native flags, which may\nsaturate.\n\n**Phase base effort:**\n- ① DESIGN: `HIGH`\n- VISUAL_DESIGN: `HIGH`\n- ② BUILD: `LOW` (auto-escalating to `STANDARD` → `HIGH` after failures)\n- ③ REVIEW: `HIGH`\n- ④ DEPLOY_DESIGN: `HIGH`\n- ⑤ DEPLOY_EXECUTE: `LOW` (auto-escalating)\n- ⑥ DEPLOY_REVIEW: `HIGH`\n\n`Phase` also carries `DEPLOY` (a legacy single-phase bridge, base `LOW`) and\n`ABANDONED`; the phase diagram omits them deliberately.\n\nSee ADR-0006 (normalized effort ladder) and `domain\u002Feffort.py`.\n\n## Capacity states\n\n`Available | WindowExhausted | CreditsExhausted | AuthenticationFailed`\n\n**The one rule that matters:**\n`CreditsExhausted` has **no `resets_at` field** and can never acquire one.\nThis is enforced at three independent layers:\n1. Type-level: `domain\u002Fcapacity.py`'s dataclass has no such attribute.\n2. Property-tested: `schedule_probe(CreditsExhausted(...))` can only return a\n   `BackoffProbe`, never a `DeadlineProbe`.\n3. Database-level: the `engine_health` table has a CHECK constraint\n   `credits_never_have_a_deadline` that rejects any `INSERT`\u002F`UPDATE` with\n   `capacity_state = 'CreditsExhausted'` and non-null `resets_at`.\n\nSee `domain\u002Fcapacity.py`, `domain\u002Fcircuit.py`, the constraint in\n`migrations\u002F0007_engine_health_rotation.sql`, and the CLAUDE.md non-negotiable \"A\ncapacity rejection always outranks a completion claim\" (it has no ADR of its\nown).\n",{"name":5,"description":7,"allowed-tools":24},"Read","develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700",".claude\u002Fskills\u002Fvibey-domain-model",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add the-vibey-project\u002Fvibey --skill vibey-domain-model",{"tool":41,"command":42},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill vibey-domain-model",{"tool":44,"command":45},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill vibey-domain-model","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002F.claude\u002Fskills\u002Fvibey-domain-model\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]