| name | diagnose |
| description | Investigate failures in Gradient contracts, docs, schemas, profiles, harness
wiring, and future validation commands. Trigger: /diagnose.
|
| argument-hint | <symptom or failing artifact> |
/diagnose
Diagnose Gradient as a contract scaffold, not as an application. The likely
failure is a contradiction between docs, schemas, profiles, examples, and the
public-safe boundary.
Procedure
- Reproduce the symptom against live files or commands. Do not debug frozen
hypotheses.
- Classify the affected lifecycle stage: Intent, Work Graph, Fleet Run,
Evidence, Policy/Eval, or Feedback.
- Trace the source of truth:
- architecture:
docs/architecture.md
- module contracts:
docs/module-contracts.md
- accepted decisions:
docs/decision-log.md
- profiles:
profiles/*.yaml
- schema:
schemas/gradient.schema.json
- Find the contradiction or missing contract.
- Fix the root cause when scoped; otherwise file a concrete debt item.
Gate
The load-bearing ship gate is ./scripts/validate.sh, plus reviewer
judgment for lifecycle semantics in docs/architecture.md and
docs/module-contracts.md when docs change.
Diagnosis must not imply CI, tests, or deploy verification exist in this repo.
Name those paths as absent or unverified when they matter.
Output
Return root cause, affected lifecycle stage, evidence, fix, and any residual
unverified path.
