xeiaso.net / ircd.rs
Proof of concept mechanical port of ircnet/ircd to Rust as part of a bit about C being insecure for network services
0
Fork 0

Configure Feed

Select the types of activity you want to include in your feed.

ircd.rs / docs / claude-memory / leveva-slice-recording.md
2.0 kB

name: leveva-slice-recording description: How to record a leveva P11 feature slice (plan file + p11.md + PLAN.md row) and the TDD/inverse-invariant discipline the user expects metadata: node_type: memory type: feedback originSessionId: 2421e25a-47e2-42c2-820a-e3b2195f771e#

Each substantive leveva change is a numbered P11 slice. To record one (the user pointed at the P5 [command-cluster-port] skill for this discipline even though that skill itself is P5-only/retired):

  1. Plan file under docs/superpowers/plans/YYYY-MM-DD-p11-slice<N>-<slug>.md (Goal / Locked decisions / Design / Tests / Divergences / Gate).
  2. Progress entry appended to docs/progress-log/p11.md — append via shell heredoc (cat >> … <<'EOF'), do not Read+Edit (the log is huge). Header ## YYYY-MM-DD — P11 slice <N>: <title>, then ### Mechanism / Divergences / Tests / Docs, a **Plan:** pointer, and a **Gate:** line.
  3. PLAN.md P11 row: bump the **Done: N slices** count and append a concise ; <N> = … clause. Keep it to one clause — see [[plan-md-rows-stay-thin]].

Find the next slice number with grep -n "slice 5" docs/progress-log/p11.md.

Why: the project is a strangler-fig migration where every step is logged and gated; an un-recorded slice breaks that provenance chain.

How to apply (the discipline that matters most): write the failing test FIRST, and test the inverse invariants, not just the happy path — for every "X happens" assert the matching "X does not happen when it shouldn't" (non-match ignored, already-applied not duplicated, removal doesn't undo a prior grant, non-member skipped). Gate = cargo test -p leveva green + cargo clippy -p leveva --tests clean + cargo build --workspace 0 warnings. Commit discipline: [[commit-one-test-per-commit]], on master directly ([[work-on-master-directly]]). Related: [[leveva-ircv3-track]], [[leveva-command-folder]].