Implement consistency architecture (10-principle framework)

Adds:
- ARCHITECTURE.md: Full documentation of 3-layer system
- Context Pipeline: Preprocessing layer (pipeline.js)
- Workflow Router: 4 fixed workflows (coding, debug, deploy, audit)
- Validation Layer: Post-response quality gate (validator.js)
- Format Templates: Structured output templates
- TOOLS.md: Beavault connection documentation

Architecture:
- Layer 1: Behavior rules (always injected)
- Layer 2: Persistent facts (structured memory)
- Layer 3: Ephemeral context
- Priority enforcement: Rules > Prefs > Task > Chat
- Memory write policy: Only confirmed fixes, repeated preferences
This commit is contained in:
JC Beasley
2026-07-04 15:44:53 -07:00
parent 6ad8772e48
commit ed5dff8ebd
9 changed files with 829 additions and 0 deletions
+46
View File
@@ -0,0 +1,46 @@
# Workflow: Deployment
## Intent Classification
**Triggers:** Deploy to staging/production, release, infrastructure changes
## Fixed Output Format
```markdown
## Deployment Summary
[What and where]
## Pre-Deployment
- [x] Backup created
- [x] Tests pass
- [x] Rollback plan documented
## Changes Applied
| Step | Command | Status |
|------|---------|--------|
| 1 | [command] | ✅ |
| 2 | [command] | ✅ |
## Verification
- [x] Service responding: [url]
- [x] Logs normal: [check]
- [x] Smoke test: [result]
## Rollback (if needed)
[Exact rollback steps]
```
## Tool Access Rules
1. **Check first** - current state before changing
2. **Backup** - always before production changes
3. **Verify** - process running, endpoint responding, output correct
4. **Document** - update RUNBOOK.md if procedure changed
## Constraints
- NO: Deployment without verification plan
- NO: "It should work" = done
- NO: Blurry rollback steps
- YES: Status checked and reported
- YES: Rollback tested if possible