docs(solutions): column-agent execution-principal blast-radius learning#1456
Conversation
… checklist + column-agent vocabulary
|
Too many files changed? Review this PR in Change Stack to see how the pieces fit before you dive in. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds documentation for execution-principal agent binding in the experimental workflow columns model. It introduces two key concepts—Column agent and Effective agent—then provides a comprehensive architecture-pattern guide detailing which subsystems must be re-keyed when execution identity is overridden per entity. ChangesAgent Execution Principal Glossary & Override Pattern
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryDocumentation-only PR capturing institutional learning from the column-agent-assignment feature (PR #1432). No runtime changes.
Confidence Score: 5/5Documentation-only change with no runtime impact; safe to merge. Both changed files are pure documentation. The new CONCEPTS.md definitions are placed correctly within the Workflow columns & traits section, the YAML frontmatter in the learning doc contains all required fields, and both No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["Work item dispatched"] --> B{"Column has agent binding?"}
B -- No --> C["Use task.assignedAgentId\n(legacy resolution)"]
B -- Yes --> D{"Binding mode?"}
D -- defer --> E{"Work carries own agent\nor complete model pair?"}
E -- Yes --> C
E -- No --> F["Effective agent =\nColumn agent"]
D -- override --> F
F --> G["Re-key ALL identity-keyed subsystems"]
G --> G1["1. Session identity\n(model, persona, attribution)"]
G --> G2["2. Permission gating\n(buildActionGateContext)"]
G --> G3["3. Heartbeat serialization\n(both directions)"]
G --> G4["4. Resume queries\n(effective identity pass)"]
G --> G5["5. Change detection / hot-swap\n(release branch too)"]
G --> G6["6. Kill-switch parity\n(every entry point)"]
G --> G7["7. Write-surface parity\n(shared validator)"]
Reviews (1): Last reviewed commit: "docs(solutions): per-entity execution-pr..." | Re-trigger Greptile |
Summary
Captures the institutional learning from the column-agent-assignment feature (#1432), which merged before the compound pass landed on its branch.
docs/solutions/architecture-patterns/per-entity-execution-principal-override-blast-radius.md: when work can run as an identity other than the one stored on the entity, seven subsystems must be re-keyed in one design pass (session identity, permission gating, heartbeat serialization in both directions, resume queries, hot-swap/release invalidation, kill-switch flag parity, write-surface parity for safety gates). Each was discovered separately and at increasing cost across plan review, code review, and two PR-bot rounds — the checklist converts that into one up-front pass.Docs-only; no runtime changes.
Post-Deploy Monitoring & Validation
No additional operational monitoring required — documentation-only change.
Summary by CodeRabbit