You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[TK-007] No --pipe flag; FAMILY.md clause 7 breach #21
grep -rn -- '--pipe' across *.py *.md *.json *.txt *.mjs *.cjs *.yml (excluding .venv) → zero hits
git grep across all local heads (family/verdict-ingest, main, family/skill-md) → zero hits
Near-miss that does not discharge the clause:tablekit verdict (tablekit/cli.py:421) reads stdin — but only to ingest srdcheck's --tracerequest.completed events into the ledger. No table-kit command accepts table-kit's own input on stdin.
Note table-kit is transport + session ledger rather than a verdict tool, so clause 1's verdict semantics apply to it only where it emits a verdict — but clause 7's surface obligations apply in full, and both the README and SKILL.md link FAMILY.md as the governing contract.
Found by a conformance audit of the check-family four (srdcheck, charactercheck, dmcheck, table-kit) against FAMILY.md v1 on 2026-08-17. Audited at working-tree HEAD, which was 1–3 commits ahead of origin/main and 0 behind, so absences hold for main. Every claim below was verified by execution or by git grep across all local heads, then independently re-derived by a second pass instructed to refute it.
Clause 7 is now stated per member class, and table-kit is classed transport — hybrid-table transport plus a session ledger, not a verdict tool.
--pipe is one-query-in / one-verdict-out. That shape is what a verdict tool is; a component that records a session has no such shape, so implementing --pipe here would produce a surface with no honest semantics — built to satisfy a table rather than to be used. v2 says so explicitly rather than leaving the gap implied:
--pipe is one-query-in / one-verdict-out. It binds the verdict class because that shape is what a verdict tool is; a transport that records a session has no such shape, and requiring it there would produce a surface with no honest semantics.
The evidence in this issue was correct — there is no --pipe, verified by execution and git grep across all heads. What changed is that the clause no longer binds this repo.
Still binding on table-kit and still open: #23 (--schema must be a flag, not only a subcommand — that one binds every class).
Activity
chaoz23 commentedon Aug 20, 2026
Closing as won't-fix under FAMILY.md v2 (chaoz23/srdcheck#83, merged).
Clause 7 is now stated per member class, and table-kit is classed transport — hybrid-table transport plus a session ledger, not a verdict tool.
--pipeis one-query-in / one-verdict-out. That shape is what a verdict tool is; a component that records a session has no such shape, so implementing--pipehere would produce a surface with no honest semantics — built to satisfy a table rather than to be used. v2 says so explicitly rather than leaving the gap implied:The evidence in this issue was correct — there is no
--pipe, verified by execution andgit grepacross all heads. What changed is that the clause no longer binds this repo.Still binding on table-kit and still open: #23 (
--schemamust be a flag, not only a subcommand — that one binds every class).chore: declare family_class = transport in tool.json (#27)