Cortex

Cortex is an assistant that runs inside a Tenzro node for the node's operator. It reads the state of the node and the network, answers questions about them, drafts settings such as the next burn rate from its forecast of demand and supply, and talks to other operators' nodes over signed envelopes. Every answer is a signed decision record. Any action Cortex proposes runs only if the operator's signed policy allows it; anything else is held as a proposal until the operator approves or rejects it.

Cortex is operator-only. Apart from tenzro_cortexStatus, every Cortex method is an admin method: the node's access policy admits the operator DID or a policy admin, and refuses everyone else before the handler runs.

Status

Anyone can ask whether a node's Cortex is enabled, whether the node's role requires it, which model it runs and its state (disabled, loading, healthy or unavailable):

tenzro cortex status --rpc https://rpc.tenzro.com

Ask

tenzro cortex ask "Which peers have missed SLA probes this epoch, and why?"

The answer is a decision record signed by the node: the trigger, a snapshot of the state Cortex read, the policy in force, the model's output, the typed action it proposes and the outcome.

Decisions, proposals and reverts

# The decision log, newest first; --jsonl writes it as training records
tenzro cortex decisions --limit 20

# Actions held because no signed policy grant allows them
tenzro cortex proposals
tenzro cortex approve <PROPOSAL_ID>
tenzro cortex reject <PROPOSAL_ID>

# Undo an action Cortex ran, by running its recorded inverse
tenzro cortex revert <DECISION_ID>

Because every action has a recorded inverse, an operator can let Cortex act within a narrow policy and still undo any single step.

Forecasts and drafts

tenzro cortex forecast --series <SERIES>
tenzro cortex burn-draft

The forecast is Cortex's view of network demand and supply. The burn draft is its proposal for the next burn-rate setting, with the inputs it used. A draft changes nothing on its own: network parameters change only through governance.

Talking to other nodes

Cortex sends signed envelopes to validators and RPC operators and records their signed acknowledgements:

tenzro cortex send --to did:tenzro:machine:... --body "Your node is lagging two checkpoints behind" \
  --endpoint https://<peer-rpc>
tenzro cortex messages
tenzro cortex liveness --peer-did did:tenzro:machine:... --endpoint https://<peer-rpc>

Methods

Related

• Operators and roles
• RPC access
• Token economics for the burn rate