natsukium/felis
Archived
Watch
1
Code Issues 23 Pull requests Projects Releases 6 Packages Wiki Activity Actions

docs: reconcile the vt-compliance record rule with doc-cascade's default-no-record gate #390

Closed
opened 2026-09-25 00:48:16 +09:00 by natsukium · 1 comment
natsukium commented 2026-09-25 00:48:16 +09:00
Owner
Copy link

docs/explanation/protocols/vt-compliance.md (~66-67) says "any added or removed sequence is a breaking change and needs its rationale recorded in this doc". The add-escape-sequence skill echoes this. It conflicts with doc-cascade's "Default to no record" gate. docs/explanation/protocols/landscape.md is already the home for admission decisions.

Pick one policy:

  • (a) narrow the vt-compliance rule to admission decisions that pass the record gate, recorded in landscape.md; or
  • (b) keep it, and state it in doc-cascade as an explicit exception.

Then align the skill.

`docs/explanation/protocols/vt-compliance.md` (~66-67) says "any added or removed sequence is a breaking change and needs its rationale recorded in this doc". The add-escape-sequence skill echoes this. It conflicts with doc-cascade's "Default to no record" gate. `docs/explanation/protocols/landscape.md` is already the home for admission decisions. Pick one policy: - (a) narrow the vt-compliance rule to admission decisions that pass the record gate, recorded in landscape.md; or - (b) keep it, and state it in doc-cascade as an explicit exception. Then align the skill.
natsukium commented 2026-09-25 11:45:18 +09:00
Author
Owner
Copy link

Decision: (a). Narrow the vt-compliance rule to admission decisions that pass doc-cascade's record gate, recorded in docs/explanation/protocols/landscape.md; align the add-escape-sequence skill.

Decision: (a). Narrow the vt-compliance rule to admission decisions that pass doc-cascade's record gate, recorded in `docs/explanation/protocols/landscape.md`; align the add-escape-sequence skill.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
v0.1.0-rc.9
v0.1.0-rc.8
v0.1.0-rc.7
v0.1.0-rc.6
v0.1.0-rc.5
v0.1.0-rc.4
v0.1.0-rc.3
v0.1.0-rc.2
v0.1.0-rc.1
Labels
Clear labels   
priority/P0
Must be resolved before the v0.1.0 tag

  
priority/P1
Must be settled before the first public contract freezes

  
priority/P2
Explicitly deferred until after v0.1.0

  
release/v0.1.0
Work tracked for the first tagged release

  
status/blocked
Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  
status/planned
Triaged with a source-grounded plan and a passed pi review; ready to implement

  
type/bug
Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  
type/design
An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  
type/test-gap
Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  
type/tracker
Parent issue that tracks child work

No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
natsukium/felis#390
No description provided.