Sign inAI & AGENT INVENTORY
Build an inventory your team can review.
Build your inventory from team records and reviewed documents. Record each system’s purpose, owner and dependencies.
FORAI program owners, technology teams and business sponsors
THE WORK THIS CONNECTS
How this works
in your workspace.
Use your systems and source documents to build the record. Review proposed connections before they become part of your governance workflow.
A useful system register
Record why a system exists, who is accountable and where human judgment enters the process.
A dependency map
Connect the use case to its vendor, model, data sources and downstream business process.
A review boundary
Identify which changes require another look: a new purpose, model version, retrieval source or agent permission.
How records enter the product and who reviews them
- Inputs
- Known applications and agents, intended uses, owners, vendor/procurement and IT records, model/deployment details, data categories and decision impact.
- How information is collected
- Register known systems and owners from team records. Add source documents and review proposed records before accepting them. Discovery connectors are separate from this intake workflow.
- Who confirms it
- Business owners confirm use, IT confirms technical facts, and the customer governance lead signs off scope and unresolved gaps.
- What you receive
- An AI/use-case register, dependency map, named owners, documented risk observations and a completeness/exclusion list.
Your team registers known systems and reviews the records proposed from its documents. Source owners confirm facts; authorized reviewers decide which mappings and observations to accept. The inventory shows the scope you have supplied, with gaps and unresolved assertions kept visible.
IN YOUR WORKSPACE
Put the record
to work.
Start with the sample records, then add your systems and documents. Inspect the evidence, record your review and assign follow-up work.
Start with a private workspace