01
Repository instructions
Tell coding agents when company work should use Tribble instead of calling a model directly.
Product / Agent interface
Let coding agents discover how your company works.
Publish machine-readable instructions, reusable procedures, approved tools, and company knowledge so agents know when and how to use Tribble.
- System
- Agent interface
- Focus
- Discover. Route. Verify.
- State
- Instructions published
- Output
- Execution receipt
AGT-310Instructions published
An agent should find the company's approved way to do the job before improvising its own.
Tribble publishes the instructions and tools that coding agents, enterprise assistants, and customer-built applications need to find approved company knowledge and reusable procedures.
The instructions help an agent choose the right path. They do not bypass company rules. Tribble still decides which data, tools, models, regions, and actions are allowed for the request.
02
Reusable procedures
Package the evidence, tools, checks, and stopping rules for work the company does repeatedly.
03
Approved tools and data
Expose only the resources and actions approved for that deployment through MCP and APIs.
04
Execution receipt
Show which company knowledge, procedure, rule, model, and approval shaped the result.
The agent finds the company's approved way to do the job before improvising.
Published instructions point the agent to Tribble. Company rules still control the data, tools, models, and actions it may use.
01
Discover
Read local guidance, installed skills, and the approved enterprise capability catalog.
02
Resolve
Ask Tribble whether approved company knowledge, current sources, a procedure, tools, or a model are required.
03
Execute
Run only the permitted route with data, provider, region, quality, and approval rules attached.
04
Return
Deliver the result with evidence and preserve reviewed outcomes for future reuse.
How agents connect
Publish clear instructions. Keep company rules in control.
Give agents local instructions for choosing Tribble, reusable procedures for repeated work, approved tools and data for live tasks, and a receipt that explains what happened.
Open the template catalogAGENTS.md
Repository guidanceTell coding agents when company knowledge, an approved procedure, or company-controlled execution should go through Tribble.
Open templateSKILL.md
Reusable procedurePackage task-specific discovery, evidence, execution, verification, and stop conditions without loading an entire operating manual into every request.
Open skillAgent Card (A2A)
Network discoveryAdvertise approved identity, capabilities, skills, authentication requirements, and protocol support at the enterprise boundary.
Contract statusMCP / API
Live resources and toolsExpose permitted Brain facts, procedures, route decisions, execution, and outcome capture through deployment-specific contracts.
Contract statusRoute receipt
Execution evidenceReturn the company knowledge, procedure, rule, model, quality check, and destination that shaped the result.
Read contractWhat instructions cannot do
Instructions help the agent choose. Tribble enforces the rules.
Agent files can explain the preferred path. They cannot grant access, expose credentials, or let an agent bypass company rules for data, providers, regions, quality, or approval. Tribble still decides whether direct model use is allowed.
These public files are integration templates. Production endpoints, authentication, tools, procedures, and availability depend on the approved deployment.Route receipt / example
brain_stateaccount-risk/current
procedurerenewal-brief/v3
routebrain-first
modelnot-required
evidenceattached
actionreview-required
Define the first agent workflow that should discover and reuse your company Brain.
In one working session, we map the current applications, model spend, repeated work, and the first result worth proving. You keep the map either way.