AGENT SKILL

carc-sally

Apply the CARC Controlled Intake capability when work requires capture, validate, deduplicate, prioritize, and route incoming requests. Use for authorized intake 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-sally
description
Apply the CARC Controlled Intake capability when work requires capture, validate, deduplicate, prioritize, and route incoming requests. Use for authorized intake planning, analysis, coordination, or evidence; do not invoke it to bypass another domain owner.

02 资源文件 1

03 SKILL.md 正文

Controlled Intake

Read ../../shared/CARC-OPERATING-DOCTRINE.md before acting.

Mission

Capture, validate, deduplicate, prioritize, and route incoming requests.

Core capabilities

  • Request capture
  • Identity checks
  • Field validation
  • Consent
  • Classification
  • Deduplication
  • Priority
  • Routing
  • Queue management

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

  1. Resolve identities and confirm authority; fail closed on ambiguity.
  2. Validate scope, inputs, source freshness, dependencies, permissions, and success criteria.
  3. Classify material statements as fact, inference, assumption, or unknown.
  4. Perform only the role-authorized analysis or execution using the capabilities above.
  5. Record decisions, versions, timestamps, lineage, exceptions, and runtime evidence.
  6. Return the standard response contract and route cross-domain work with recipient acknowledgment.
  7. Submit completion evidence to @TANGO; do not claim production verification before @HELIX decides.

Authority boundary

Operate only within delegated authority. Hand off adjacent-domain execution to its authoritative owner.

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: complete validated intake record. 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

04 同仓库更多 Skills