iamcxa/kc-dev-flow
Profile-native POC, Pilot, and Production delivery routes with a minimal shared authority core.
Audit, adopt, or upgrade profile-native kc-dev-flow in a brownfield repository while preserving its existing tracker, iteration authority, workflow runtime, and delivery provider.
Advise the next smallest integrated delivery step when an approved development route is unclear, blocked, drifting, or approaching a material transition. Use for normal delivery guidance; do not use as a mandatory stage review or independent assurance gate.
Recommend and ask the Captain to choose POC, Pilot, or Production before a work item enters its first working stage, or when an observed promotion trigger makes the committed profile stale.
Resume an adopted repository's approved work through its selected POC, Pilot, or Production route while loading only the shared core and selected profile-stage contract.
Provide independent technical assurance for a contested, high-risk, hard-to-reverse, or low-confidence engineering claim. Use when the Captain or First Officer needs an evidence-bound second judgment; do not use for routine delivery guidance or as a mandatory stage gate.
Compatibility alias for callers that explicitly request the legacy science-officer-em report envelope. New delivery guidance uses chief-engineer; new independent technical assurance uses science-officer.
Install, dry-run, audit, or update a deterministic one-way projection from one commissioned Spacedock workflow into GitHub Project Draft items, with optional explicit links to existing Issues. Use when a repository needs SD state visible in GitHub without making GitHub lifecycle authority, when checking an installed projection, or when reviewing the target files and external mutation plan before apply.