Advanced usage
Turn good research into a practice you can repeat.
Start here after you are comfortable asking a focused research question. Each capability below solves a different problem; choose one, use it, and add the next only when it earns its place.
Keep the layers separate #
Current evidence supports a current conclusion. Reusable context helps frame the next investigation. Past decisions help you learn. None of them automatically becomes a recommendation, an approval, or broker authority.
tcx-workflow to answer today’s question; use the capabilities below to make tomorrow’s question clearer, faster, or easier to review.Add the capability that matches your problem #
“I keep repeating the same background research.”
Use tcx-wiki to save stable company, industry, product, technology, or value-chain context. Ask explicitly before writing to the Wiki; it remains background context, not current evidence.
“I want my research method to be consistent.”
Use tcx-strategy for durable eligibility, risk, sizing, and falsifier rules. Use tcx-brain when you need a user-owned source bundle that guides inquiry. Both are scoped lifecycle tasks, not trade permissions.
“I want to learn from what I decided before.”
Use tcx-memory to retrieve, replay, review, and validate past judgments. It records what was known at the time and separates process quality from outcome quality.
“I want this checked regularly.”
Use tcx-automate to set a scheduled, report-only research or monitoring task. The scheduled task invokes the actual research skill and still follows its ordinary safety boundaries.
“I may eventually place an order.”
First learn the provider-to-order path. Connection, research, ticket, checks, approval, and final action are intentionally separate. Begin with a Paper provider whenever you are learning the flow.
Follow the protected order path →A practical working rhythm #
- Investigate. Start each material question with
$tcx-workflow, including horizon, decision, and exclusions. - Preserve the useful part. Put stable background knowledge in the Wiki, review a decision in Memory, or turn a proven method into a Strategy or Brain.
- Monitor selectively. Automate only questions where a recurring report can change your attention or next decision.
- Act only through the protected path. If an order becomes appropriate, use the dedicated provider, review, approval, and final-action flow—never an analysis prompt.
Need a precise entrypoint? #
$tcx-server can explain readiness or recovery. Neither starts research or changes your investment state.