Taxonomy
Knowing what a question is about before answering it.
What it does
Knowledge tags are derived from the material an agent is grounded in and from its connectors, and those tags are policy-aware: a tag can be visible while its underlying source is not. A tiered classifier decides whether an incoming question is inside the agent's scope, escalating from cheap pattern matching to embedding comparison only when it needs to.
Why it matters
Most bad agent answers are scope failures, not reasoning failures: the question was never one this agent should have tried. Classifying scope first turns those into a clean redirect instead of a confident invention.
How it works
Tags respect access policy
A tag derived from restricted material does not leak the existence of that material to someone who cannot see it.
Classification is tiered for cost
Cheap pattern matching runs first; embedding comparison only runs when the cheap tier is not confident.
It is not an ontology, and we do not call it one
There is no authored hierarchy, no inheritance, no schema to maintain. If you need a formal taxonomy you manage yourself, this is not it yet.
Questions
- Can I define my own taxonomy?
- Not today. Tags are derived from your material rather than authored as a scheme. An authorable hierarchy is the obvious next step and is not built.
- What happens to an out-of-scope question?
- The classifier flags it before the model commits to an answer, so the agent can redirect rather than improvise.
The rest of the bag
Your agent has its own inbox, not a share of yours.
Inbound arrives by webhook from an email provider. We do not run our own MX or SMTP servers.
Package
Export, share and install agents as portable archives.
Export, import, handoff links and showcase all work. There is no marketplace, no package versioning, and no signed packages.
Memory
Grounded retrieval over your own material, with receipts.
This is retrieval, not persistent agent memory. Vector grounding is code-complete; the vector deployment is still pending.
That was step 2 of 6: it crosses a tenant boundary. Next, for agent-to-agent traffic the edge is authorised before anything executes, and the caller token is minted for that hop alone.