Agent guide
Use this page as the public, repository-independent starting contract for an agent. It distinguishes reading public product documentation from operating an authenticated Tedix organization.
Documentation endpoints
Start with the smallest sufficient source:
| Need | Endpoint |
|---|---|
| Page inventory and summaries | https://docs.tedix.dev/llms.txt |
| Complete public corpus | https://docs.tedix.dev/llms-full.txt |
| Human navigation | https://docs.tedix.dev/ |
| Page Markdown | Follow the Markdown URL advertised on each page |
| Public REST API catalog | https://api.tedix.dev/openapi.json |
| Human API reference | https://api.tedix.dev/docs |
Prefer llms.txt, select the relevant page, and fetch only that page’s
Markdown. Use llms-full.txt when the task genuinely requires cross-document
analysis. Do not infer private implementation details from absent public
material.
The OpenAPI document describes only the curated public /v1/* REST surface.
It does not enumerate private oRPC procedures or authenticated MCP tools.
Source priority
For public product questions, use this order:
- Versioned release manifests and live documented behavior.
- Public contracts, schemas, and source from an authorized source export.
- The current public documentation corpus.
- Marketing summaries.
State when a claim is an inference. Pre-release main is inspectable but has no
compatibility or support promise; do not present it as a stable release.
Authenticated operation
Use the installed tedix CLI when an operator has authorized access to an
organization:
tedix -w acme auth status
tedix -w acme ask "Summarize the active work and cite its evidence."Here and below, replace acme with the authenticated CLI workspace.
Choose the lane deliberately:
| Lane | Use it for |
|---|---|
Home via tedix ask |
Durable work, rationale, approvals, delegation, and run evidence |
Code Mode via tedix code |
Direct, bounded discovery and stateless calls |
Work Items via tedix work |
Atomic claim, coordination, proof, and settlement |
For Code Mode, discover first:
tedix -w acme code \
'async () => await discover.search({ query: "work items", limit: 5 })'Request includeParameters: true only for the few callables you intend to use.
Never invent a callable, namespace, schema, or permission.
Authority and evidence rules
- Read-only discovery does not authorize a mutation.
- Treat write-capable calls as production changes to the selected organization.
- Human-required consent, MFA and user presence belong to the human. Other approvals go to the designated independent principal, which may be a tedi.
- A queued workflow, green test, commit, or health check proves only itself.
- For completion, read the settled run or task, relevant artifacts, mutation receipt, and live target state.
- Preserve
supportedClaims,unsupportedClaims, and evidence references from tool results. Do not upgrade partial evidence into a stronger claim. - Never request, print, or persist browser cookies, OAuth grants, API keys, or secret-provider values.
Repository agents
An authorized Tedix source export includes a root AGENTS.md with scoped
repository rules, validation commands, and architecture invariants. Read it and
the nearest scoped AGENTS.md before changing files. The public
coding-agent operating manual explains the exported layout.
For a human first run, continue with Getting started.