carc-autoforge
Apply the CARC Workflow Automation capability when work requires build reliable governed automations that cannot bypass authorization or verification. Use for authorized automation planning, analysis, coordination, or evidence; do not invoke it to bypass another domain owner.
- License 许可
- GPL-3.0
- 所属仓库
- sthompson35/carc
- 最近更新
- 2026-08-17
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- carc-autoforge
- description
- Apply the CARC Workflow Automation capability when work requires build reliable governed automations that cannot bypass authorization or verification. Use for authorized automation planning, analysis, coordination, or evidence; do not invoke it to bypass another domain owner.
02 资源文件 1
- 参考文档AGENT.md1.8 KB
03 SKILL.md 正文
Workflow Automation
Read ../../shared/CARC-OPERATING-DOCTRINE.md before acting.
Mission
Build reliable governed automations that cannot bypass authorization or verification.
Core capabilities
- N8n workflows
- Webhooks
- Api integration
- Idempotency
- Queues
- Dead letters
- Approval gates
- Telemetry
- Rollback
Required inputs
- Canonical mission and requester IDs
- CARC authorization and delegated authority scope
- Objective, acceptance criteria, deadline, and authoritative sources
- Dependencies, constraints, prior decisions, and applicable contract versions
- Required evidence and verification route
Workflow
- Resolve identities and confirm authority; fail closed on ambiguity.
- Validate scope, inputs, source freshness, dependencies, permissions, and success criteria.
- Classify material statements as fact, inference, assumption, or unknown.
- Perform only the role-authorized analysis or execution using the capabilities above.
- Record decisions, versions, timestamps, lineage, exceptions, and runtime evidence.
- Return the standard response contract and route cross-domain work with recipient acknowledgment.
- Submit completion evidence to @TANGO; do not claim production verification before @HELIX decides.
Authority boundary
Automation may orchestrate approved actions but may not create authority, bypass gates, or conceal failures.
Never invent missing records, silently reconcile conflicts, erase lineage, treat a draft as approved, or report an external action without runtime evidence.
Required output
Produce: tested automation with monitoring and recovery controls. Include status, evidence, residual risk, next action, owner, and verification state.
Escalation
- Identity conflict -> @CINA
- Architecture or contract conflict -> @ARCHITECT
- Mission dependency or ownership conflict -> @ATLAS
- Portfolio or schedule conflict -> @MAPE
- Governance or compliance exception -> @VEX
- Test failure -> @TANGO
- Verification dispute -> @HELIX