Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,4 @@ findings.jsonl

# Superpowers brainstorming scratch (visual-companion mockups)
.superpowers/
.wardline
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ clean/allowed state. warpline facts are advisory and never gate. See the
`warpline-workflow` skill for the full loop.
<!-- /warpline:instructions -->

<!-- legis:instructions:v1.1.1:6604fe0c -->
<!-- legis:instructions:v1.3.0:6604fe0c -->
## Legis (git/CI + governance)

Legis is the git/CI and governance layer of the Weft suite. Reach for it when a policy fires at the CI/git boundary and a change needs a *recordable* override or human sign-off, when you need governance attestations keyed to stable code identity (SEI), or when you need git/CI context — branches, commits, pull requests, check outcomes, and the Loomweave-bound rename feed — around the work. Enforcement is graded: agent-programmable policy cells decide whether a violation self-clears with an audit trail, is judged inline, or escalates to a human; every decision lands in an append-only, SEI-keyed audit trail that survives rename/move.
Expand Down
2 changes: 1 addition & 1 deletion CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ clean/allowed state. warpline facts are advisory and never gate. See the
`warpline-workflow` skill for the full loop.
<!-- /warpline:instructions -->

<!-- legis:instructions:v1.1.1:6604fe0c -->
<!-- legis:instructions:v1.3.0:6604fe0c -->
## Legis (git/CI + governance)

Legis is the git/CI and governance layer of the Weft suite. Reach for it when a policy fires at the CI/git boundary and a change needs a *recordable* override or human sign-off, when you need governance attestations keyed to stable code identity (SEI), or when you need git/CI context — branches, commits, pull requests, check outcomes, and the Loomweave-bound rename feed — around the work. Enforcement is graded: agent-programmable policy cells decide whether a violation self-clears with an audit trail, is judged inline, or escalates to a human; every decision lands in an append-only, SEI-keyed audit trail that survives rename/move.
Expand Down
65 changes: 0 additions & 65 deletions docs/arch-analysis-2026-06-21-1754/00-coordination.md

This file was deleted.

140 changes: 0 additions & 140 deletions docs/arch-analysis-2026-06-21-1754/01-discovery-findings.md

This file was deleted.

Loading
Loading