Documentation • Architecture • Governance • Evidence

Docs

Q: What should I read first?

Start with Agents, then Agent Specs, then the Enterprise Proof Pack, then the Pilot intake.

Q: Do pages open as real pages?

Yes. FinternetOps documentation is page-based with clear navigation and no embedded blades.

FinternetOps documentation focuses on operational truth, controls evidence, risk stress testing, and compliance explainability. Everything is designed for enterprise review: consistent structure, clear boundaries, and audit-friendly artifacts.

Browse Agents Training Pricing

Start here

Agent Library (what exists)
Agent Specs Library (how each agent works)
Enterprise Proof Pack (buyer-ready artifacts)

Core docs

Architecture

Cloud-first, controls-first design. Policy-first thinking and role-based outputs.

Read architecture IP notice

Governance

Explainability that governance can approve: what happened, why it matters, what changed.

Governance artifacts Certification

Stress testing

Liquidity + settlement scenarios with decision-ready playbooks for ops and leadership.

Stress docs Playbooks

Reporting

PDF-ready weekly briefs, incident timelines, and audit-friendly formatting.

Reporting docs Packages

AgentOps

Control plane: specs, guardrails, RBAC, logging, versioning, and change control.

AgentOps platform Agents

Start a pilot

Deploy 1–3 agents in a monitored environment. Evidence-first, procurement-friendly.

Pilot intake Pricing

FAQ

Are docs public? Yes, unless a page is explicitly marked partner-only.

Do pages open as real pages? Yes. No blades or embedded frames.

What should I read first? Agents → Specs → Enterprise Proof → Pilot.