Workflows preserve boundaries while reports move between tools.

First adoption

First adoption establishes a baseline without pretending that unsupported axes are safe. The useful result is a first report with unmeasured axes and unsupported constructs made explicit.

scan
  -> validate
  -> snapshot
  -> baseline policy
  -> first signature report

PR review

PR review compares before and after artifacts, then turns the difference into AIR, theorem precondition checks, Feature Extension Report, policy decision, and PR comment summary.

before scan
  -> after scan
  -> signature diff
  -> AIR
  -> theorem precondition check
  -> feature extension report
  -> policy decision
  -> PR comment summary

Generated change

AI-generated change provenance records provider, model, prompt ref, generated patch, and human review boundary. The provenance record supports review and reproducibility; it does not decide whether the change is good or bad.

• Prompt and generated patch Evidence refs for the generated action and its proposed scope.
• Human review boundary Whether the generated change was reviewed, and what review evidence is available.

Scheduled scan

Scheduled scans update drift ledgers and operational feedback artifacts. Daily drift is a trend artifact, not proof that a report warning caused an operational outcome.

scheduled scan
  -> signature snapshot
  -> drift ledger
  -> ownership boundary monitor
  -> operational feedback

Dynamics and forecast

Architecture Dynamics and SFT forecasting workflows hold finite support, bounded horizon, proposal refs, unknown remainder, and review recommendations apart from probability or causal forecast claims.

architecture field snapshot
  + operation proposal log
  + PR force report
  -> signature trajectory report
  -> architecture dynamics metrics report

PRD / Spec / Issue / AI proposal
  -> ArtifactDescriptor
  -> OperationSupportEstimate
  -> ForecastConeSkeleton
  -> ConsequenceEnvelope