Skip to content

What E2C consumes

External evidence and artifacts that can be adjudicated into responsibility state.

Business evidence

  • Business objectives and incomplete requirements (expected, not a blocker)
  • Workflow narratives, policies, and risk boundaries
  • Historical decisions, exceptions, and human judgment records
  • Operational context that defines what “allowed” means in your domain

Engineering & project artifacts

  • Repositories and project structures (where shareable)
  • Existing code, configs, and integration boundaries
  • Prior release gate failures or disputed admission decisions

Structured candidate intake

E2C may consume structured candidate inputs from humans, GPT, Cursor, or other model providers. These are never authority. Structured candidate intake can propose candidate slots, contracts, source-boundary hypotheses, missing-contract candidates, or next-action candidates. E2C must admit, validate, route, or block them before downstream use.

What E2C does not consume as sufficient alone

  • Raw model output without source binding
  • Informal “LGTM” without artifact trail
  • Unscoped document dumps without field discipline
  • ChatGPT / Cursor / human memory as source of truth

← Back to Documentation