docs: state what pinax has actually shipped - #21
Merged
Conversation
Six files asserted pinax is pre-code design-phase. The tree disagrees: lexis ships the six-type value system and pinax ships the Phase 01 pager, buffer pool and B+tree, across v0.0.2 (2026-07-30) and v0.0.3 (2026-08-16). SECURITY.md is the one that mattered. Its Scope section told vulnerability reporters that no implementation code had landed and only design reports were in scope -- so someone finding a real memory-safety or data-corruption bug in the pager or B+tree would have read that and not reported it. Implementation code is now named as in scope, with design reports still welcome. The status text says which crates ship code and which do not, rather than a vague "under development": hypomnema and phylaxis are genuinely empty and reserve their workspace position for later phases, so calling all four implemented would be the same error pointed the other way. Found by grepping for the claim rather than fixing only the three files the report named -- AGENTS.md, CLAUDE.md and _llm/current_state.toml carried it too.
… gate (#20) Main replaced the unsatisfiable trailer-only gate with the fleet hybrid gate and branch protection now requires gate / gate. Merging main so this PR can report the new required context.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Finding
Six files assert pinax is pre-code design-phase. The tree disagrees.
SECURITY.mdis the one that matters. Its Scope section reads:That tells a vulnerability reporter that implementation-code issues are out of scope. Someone
finding a real memory-safety or data-corruption bug in the pager or B+tree would read it and not
report.
Evidence
Contradicted at
origin/main:CHANGELOG.mdv0.0.2 (2026-07-30, "stand up the pinax workspace and implement lexis") and v0.0.3(2026-08-16, "implement Phase 01 pager, buffer pool, and B+tree")
README.md: "Status: Phase 01 (pager / buffer pool / B-tree) implemented"Cargo.tomlworkspace members:hypomnema,lexis,phylaxis,pinaxStale claim sites:
SECURITY.md:11,llms.txt:3,_llm/architecture.toml:8, plusAGENTS.md,CLAUDE.md, and_llm/current_state.toml— the last three found by grepping for the claim ratherthan fixing only the files an earlier report had named.
Desired correction
State what has actually shipped, per crate. Not "all four crates are implemented" —
hypomnemaand
phylaxisare genuinely empty and reserve their workspace position for later phases, so thatwould be the same error pointed the other way. The status now says which crates ship code and which
do not.
SECURITY.mdnames implementation code as in scope (memory safety, data corruption, and — oncethose phases land — encryption and auth), with design reports still welcome.
Done when: no file in the repo asserts pinax has no implementation code.
Verification note
Docs-only; no behavioural change and no check-run name touched. Relevant because GitHub Actions is
recovering from a major outage (incident 2026-08-26T15:11:58Z) — I will not merge on an empty
rollup.