Skip to content

Getting Started

SocioProphet is not open for ambient self-serve subscriptions.

The platform is being introduced through guided onboarding, institutional deployment, and public-safe documentation. That is intentional. The system is designed as a governed operational stack, not as an unbounded sign-up funnel.

1. Start with the right path

Pick the path that matches what you are actually trying to do.

Learning and exploration

Use this path when the goal is to understand the architecture, the learning model, and the public-safe theory.

Read:

Institutional deployment

Use this path when evaluating SocioProphet for an organization, program, mission-aligned institution, or governed operational environment.

Read:

Then go to:

Analytics, identity, and evidence

Use this path when the main interest is governed identity, merge controls, event modeling, proof artifacts, and boundary evidence.

Read:

Governed operations and defense

Use this path when the interest is bounded execution, operator workflows, defensive validation, and governance of sensitive capability.

Read:

2. What the public docs include

The public docs include:

  • architecture
  • governance
  • safety boundaries
  • bounded-execution model
  • evidence and provenance model
  • public-safe product positioning
  • institutional deployment framing

3. What the public docs do not include

The public docs do not include:

  • sensitive operator kits
  • exact tactical playbooks
  • exploit or persistence workflows
  • high-fidelity adversary mechanics
  • restricted thresholds and internals that materially raise misuse value

That line is deliberate and part of the system design.

For most readers, this order works:

  1. Architecture
  2. Deterministic AI and Mathematical Safety
  3. Organizations Governance and Institutional Safety
  4. Governed AI and Cybernetics
  5. Entity Analytics Reference
  6. Public vs Restricted Security Boundary

5. Use this page

Use this page to choose the right reading path.

Use the organizations pages for deployment conversations.

Use the docs landing surface for the broader manual map.

Use the public docs to understand the system honestly, including the parts we restrict.