What Poly knows about your business, and why it is allowed to know it.
A model does not arrive understanding your business. Your dedicated expert turns what your team knows into maintained records the AI can actually use — with a permission boundary around every one of them.
Not everything said becomes something the AI should rely on.
The distinction between a conversation, a piece of scoped work, and approved durable knowledge is what keeps the context trustworthy.
Discussion
Something someone said in a meeting or a thread. Useful, unverified, and not yet a rule the AI should act on.
Scoped work
A task with a boundary: what is being answered, for whom, and what would make it acceptable.
Durable knowledge
An approved definition, decision, or rule with an owner and a review date. This is what the AI is allowed to lean on.
The inputs to good work, kept current on purpose.
Where the context actually lives.
Four screens covering knowledge, decisions, the dictionary, and the boundary.
Context is scoped, not universal.
Roles determine general capabilities. Teams and object sharing determine which building blocks a user can reach. Poly and its agents inherit the authorizing user’s boundary — never more.
An agent acting for someone on the revenue team can see and change exactly what that person can — company, region, team, and object scope included.
A graph, not a folder of documents.
Business concepts, goals, rules, and every object in the system — connected, so retrieving one thing brings the things it depends on.
Where the weekly conversation becomes work.
Bring the knowledge that lives in one person’s head.
The definition everyone argues about, or the rule only one person knows.
Book a working session