AgentProof

This is a shortcut form — environment + agent created together.

The first-class flow is /workspace/environments (create environment) → open the environment → add agent inside it. Environments are first-class objects so multiple agents share the same environment, readiness rollup, and Radar impact.

Manual non-Microsoft agent

Add an agent from any platform

AgentProof runs the same readiness review for any platform — describe your agent in plain language.

  1. Describe your agent

    What does the agent do, who does it serve, what must it never do?

    • Knowledge-retrieval agent for the internal HR knowledge base.
    • Task agent that drafts customer-support replies for human approval.
    • Autonomous agent that triages incoming security alerts.
  2. Describe the platform

    AgentProof works the same for any platform — name it briefly.

    • Custom LangChain stack hosted in AWS.
    • Open-source LLM behind an internal API gateway.
    • Vendor agent SDK deployed in our private cloud.
  3. Capability zone

    AgentProof classifies the agent into Zone 1, 2, or 3 — read the zone explainer next.

    • Zone 1 — Knowledge / Retrieval Agent.
    • Zone 2 — Task / Tool-Assisted Agent.
    • Zone 3 — Autonomous Action Agent.
  4. List the documented evidence

    What documents exist already? Intended-use statement, owner, tool permission register, audit log, monitoring cadence.

    • One-paragraph intended-use statement (versioned).
    • Named business owner + backup.
    • Tool permission register reviewed quarterly.
  5. Start the assessment

    AgentProof runs the same source-bound assessment as for Microsoft.

    • Capability + risk modifier questions tailored to the zone.
    • Evidence-confidence questions tailored to the source list.
    • Multi-select questions for tool registers and oversight rules.
  6. Generate the report

    Same report shape as Microsoft — capability zone, controls, evidence, references, compatibility panel.

    • Score band + verdict.
    • Source-bound recommended controls.
    • Compatibility note for future intelligence-pack changes.
  7. Improvement cycle

    Pick priorities, define target outcome, mark ready for reassessment.

    • Strengthen evidence on the named risks.
    • Document the autonomy boundary.
    • Add an escalation route.

Source label: User-declared manual. AgentProof never makes a legal compliance / certification / audit claim.

Manual non-Microsoft agent

Add a non-Microsoft agent

Describe a website chatbot, internal agent, OpenAI-style agent, or workflow automation agent. AgentProof will not claim the agent was technically discovered.

Evidence confidence: Low with only a short description; Strong with description + documentation + ownership + platform.