tcx-workflow

Describe the outcome and constraints #

Start a new native Codex task and invoke $tcx-workflow, either as the plain token or its matching workspace skill link. Then write the outcome you need, the time horizon, the questions that matter, and the limits that must remain in force. Natural language is expected; exclusions such as “No valuation” and “No order” are binding.

$tcx-workflow
Analyze MSFT as a medium-term quality compounder. Include contrary evidence and invalidation conditions. No order.

What happens during the run #

1. Take the smallest path. A narrow trusted fact or recorded status can be answered directly.
2. Begin when needed. Fresh research or decision work receives lightweight run provenance.
3. Choose useful expertise. Head Manager prefers exact role profiles, follows up with an owner for corrections, and may use a bounded generic child when a profile is unavailable.
4. Route sources once. One owner reuses existing evidence, then tries one user capability, optional OpenBB, official sources, other credible sources, and finally states a gap.
5. Calculate reproducibly. Numeric roles use the separate tcx-calc runtime and record conclusion-relevant inputs and results.
6. Persist when valuable. Decision-, reuse-, audit-, or handoff-relevant work becomes an authenticated artifact; narrow answers can remain direct.
7. Synthesize or stop. New evidence can trigger correction, a new perspective, independent review, synthesis, or an explicit gap.

Read Dynamic workflow for the role-profile and evidence-reassessment model.

What you receive #

The result is a current evidence-based answer or Decision Package with source/as-of posture, uncertainty, contrary evidence, missing evidence, and a recorded handoff state. The exact set of artifacts depends on the question; a simple factual request can remain small.