runtime-slice-design
Designs buildable slices of the Master FinHub Python runtime (agent loop, context compaction, safety/sandbox, router, DAG engine, message bus, docker sandbox, MCP client, SSE server, evals) or the adoption of one backlog capability into the finhub-harness plugin, agents or runtime, from the reference port maps; each design has files, typed interfaces or insertion anchors, a proof, a test plan with mutation targets, and an Authority List mapping every claim to references/<submodule>/<path>:<line>. Use for: design the slices, slice plan, redesign slice N, design the adoption of C3, revise rejected claims, update the design after I changed the spec. Also read by runtime-builder before building. Not for general Python architecture outside this repo or for designing MCP servers (Mercury, Twilio or any other).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- runtime-slice-design
- description
- Designs buildable slices of the Master FinHub Python runtime (agent loop, context compaction, safety/sandbox, router, DAG engine, message bus, docker sandbox, MCP client, SSE server, evals) or the adoption of one backlog capability into the finhub-harness plugin, agents or runtime, from the reference port maps; each design has files, typed interfaces or insertion anchors, a proof, a test plan with mutation targets, and an Authority List mapping every claim to references/<submodule>/<path>:<line>. Use for: design the slices, slice plan, redesign slice N, design the adoption of C3, revise rejected claims, update the design after I changed the spec. Also read by runtime-builder before building. Not for general Python architecture outside this repo or for designing MCP servers (Mercury, Twilio or any other).
02 资源文件 2
- 参考文档references/authority-list.md3.2 KB
- 参考文档references/slice-template.md3.2 KB
03 SKILL.md 正文
Runtime Slice Design
Turn the fourteen port maps into an ordered set of small, independently provable slices, or one backlog row into one provable adoption. Each slice must be buildable in one builder call and verifiable by four commands; anything bigger hides failures.
Steps
- Read every port map (
_workspace/01_reference-miner_*_portmap.md). Note which haveStatus: PARTIALor empty Findings — claims depending on them must be marked, not invented. - Follow the slice order in
.claude/skills/master-finhub-orchestrator/references/phase-table.md(Part B). Do not reorder: later slices assume earlier interfaces (the router in 4 plugs into the loop from 1; the DAG in 6 runs the checkpoint from 5). - Write each slice using
references/slice-template.md: files, interfaces with Python type signatures, proof test, deps, ported-vs-net-new, quant guardrails if relevant, and the cost statement for any refusal, prompt or required step the slice adds (skills/finhub-harness/references/quality-gates.mdsection 3-11; adapted from references/openrig/CONTRIBUTING.md:29-31 (Apache-2.0)). - Write the Authority List at the end per
references/authority-list.md. Every design claim that relies on how a reference does something gets a row; net-new decisions get aNET-NEWrow with a reason. Then runpython3 skills/finhub-harness/scripts/cite_check.py <design file>from the project root and fix everyBADline before step 5; on exit 3 name the submodules it could not read in the "design ready" message (skills/finhub-harness/references/quality-gates.mdsection 1-4). - Signal the judge ("design ready") and wait. On a verdict with REJECTED > 0, fix only those claims and the slice text they support.
Design rules and why
- Python 3.12, stdlib first. Every dependency is a supply-chain and licence question; slices 1–3, 5–7 and 11 need none.
graphlib.TopologicalSorterovergraphonfor the DAG — dify pins an external package we would then have to audit. - Protocols at seams. The LLM is a
typing.Protocolwith aFakeLLMfor tests, so no slice before 4 needs network or keys. Tools declare a schema the loop validates against — boundary-qa compares these shapes directly. - Proof = one command or one test. If you cannot state the proof in one line, the slice is too big; split it.
- Mypy-strict friendly. Declare return types, avoid
Anyat public boundaries, usedataclass(frozen=True)for messages and checkpoints (immutable data is easier to checkpoint and resume). - Safety slices are policy-driven and small. Slice 3 and 8 are net-new where references lack them; keep each ≤80 lines and explain the denylist in the Authority List as
NET-NEW (spec requirement). - Quant correctness is designed in. Any slice touching evals, verifiers, backtests or pricing states how it handles each guardrail in
.claude/skills/adversarial-audit/references/quant-guardrails.md. The judge will check those rows regardless. - Licences. Never cite
references/autogpt/autogpt_platform/; dify claims arepatternonly. Citations outsidereferences/are invalid. - Synthetic data only. Example payloads in the design use placeholder names (
client_a,acct_001), never real people, accounts or Mercury records.
Output
_workspace/02_strategy-architect_slices.md:
# Master FinHub runtime — slice design (revision 1)
## Slice 1 — loop + echo tool + CLI
...(slice-template sections)...
## Slice 2 — context compaction
...
## Authority List
| id | claim | evidence | slice |
|---|---|---|---|
| A1 | ... | references/...:42 | 1 |
Adoption design (one backlog item)
When the prompt names a backlog row (C3) instead of a slice range, write _workspace/02_strategy-architect_<item-id>.md with these sections, in this order: ## Source (the backlog row and its port-map rows, re-opened), ## Target (plugin skill / agent / runtime module / docs, and the exact files), ## Design (for code: files and typed interfaces; for prose: each insertion as anchor line quoted verbatim + the text to insert + the one-line attribution adapted from references/<repo>/<path>:<line> (<licence>)), ## Proof (the commands or greps that show every insertion or interface landed, with expected counts), ## Test plan (unit cases, must-still-pass list, and at least three mutation targets QA can apply on a scratch copy, each with the one test id it should break and the text of the assertion it should trip (test and sig, skills/finhub-harness/references/quality-gates.md §3-4; required in an adoption's plan, optional in a runtime slice's, and the judge checks that each sig occurs in a test; adapted from references/openrig/packages/test-system/ci/result.mjs:33-34 (Apache-2.0)), ## Does not cover (honest limits and known false positives), then ## Cost statement (one row per refusal, prompt or required step the adoption adds, with scenario, who causes it and cost to others, or the one line Cost statement: none; this design adds no refusal, prompt or required step.), then ## Authority List. Keep existing tests unmodified; a design that needs an existing test changed says why in ## Design. A prose adoption never pastes source prose: an 8-word run identical to the source is a defect. Before saying an adoption design is ready, run the cite check of step 4 on it and fix every BAD line (skills/finhub-harness/references/quality-gates.md section 1-4).
On revision
Read the latest verdict for your design (02_adversarial-risk-judge_verdict.md for runtime slices; 02_adversarial-risk-judge_<item-id>_r<k>.md with the highest k for an adoption). Change only REJECTED/UNVERIFIED claims; keep UPHELD rows byte-identical so the judge can carry them forward. Bump the revision number in the title and list changed claim ids at the top under ## Changes in revision N. If you believe a rejection is wrong, reply to the judge with the exact line as new evidence rather than resubmitting the same claim.
For the builder
runtime-builder reads this skill to understand the slice template, then implements only UPHELD claims for its slice. Interfaces declared here are the contract boundary-qa checks against — if the builder must deviate, it records why in its report.
04 同仓库更多 Skills
linky
Fixture whose links and bundled-file mentions all resolve. Use to prove no false errors.
dup-one
Second owner of the name. Use for the duplicate fixture.
dup-one
First owner of the name. Use for the duplicate fixture.
nested
暂无简介
broken
Fixture with one defect per rule. Use to prove each rule fires.
notes-style
House style for client notes. Use when writing or editing a client note.