Capability map

Capabilities for traceable investigation.

TOYTOCOL connects investigative work without collapsing uncertainty into an automated answer. Each capability supports a visible path from discovery to accountable verification.

InvestigationGoverned context
DiscoverEvidenceReasoningFindingsVerification
Conceptual capability map: investigative context connects discovery, evidence, reasoning, findings, and verification.

Capability status

  • AvailablePresent at the approved source boundary; not a production-readiness claim.
  • FoundationA bounded technical basis exists, with important experience or integration work remaining.
  • In developmentActive capability work, not represented as available.
  • RoadmapFuture direction only; sequence and scope may change.

Capability families

A governed system of work, not a collection of black boxes.

Status labels describe the approved source boundary. They do not imply autonomous truth, general availability, regulatory certification, or production readiness.

01Available

Discover

Capture observations and candidate signals so potentially relevant information can enter structured attention.

  • Observation and signal context
  • Explicit transition into investigation
  • No automatic truth designation
02Available

Investigate

Create a bounded workspace around a question, participants, evidence, analytical activity, and accountable outcomes.

  • Investigation-scoped collaboration
  • Participants, notes, discussion, and timeline
  • Shared context across working surfaces
03Available

Evidence

Persist source material and its relationships so provenance, relevance, support, challenge, and context remain inspectable.

  • Source and attachment context
  • Links to arguments and findings
  • Verification state remains distinct
04Available

Findings

Record bounded conclusions as canonical investigative outcomes with provenance and a governed verification lifecycle.

  • Evidence-connected conclusions
  • Pending and reviewed states
  • Limits and uncertainty preserved
05Available

Reasoning

Separate deterministic structural checks from persistent, human-authored analytical reasoning.

  • Structural readiness evaluation
  • Hypotheses, arguments, and evidence references
  • Qualitative confidence—not probability or truth
06Foundation

Graph

Represent investigation-scoped entities and explicit relationships as nodes and edges for inspection.

  • Authorized scoped data foundation
  • Connection and path structure
  • Live workspace renderer not yet connected
07Available

Verification

Keep human verification decisions separate from analytical confidence and retain a reviewable decision history.

  • Explicit Finding decisions
  • Current state plus recorded history
  • Verification does not equal absolute truth
08Available

Governance

Apply resource-scoped authorization and accountable participation to investigative actions and information.

  • Owner, Investigator, and Observer responsibilities
  • Resource and participation boundaries
  • Auditable investigative lifecycle
09Foundation

Extensibility

Establish bounded capability contracts that can support optional extensions without weakening the core.

  • Capability-contract foundation
  • Base web experience installs no optional packs
  • Ecosystem delivery remains future work

Connected responsibilities

Capabilities reinforce a single traceable record.

Discovery establishes context. Investigation governs the work. Evidence and reasoning support a Finding. Verification records the accountable decision. Governance constrains every stage.

Important: the sequence structures human work. It does not automatically transform data into truth.

  1. 01DiscoverNotice and qualify
  2. 02InvestigateBound the question
  3. 03Evidence + ReasoningConnect and inspect
  4. 04FindingState the conclusion
  5. 05VerificationRecord human review

Ecosystem direction

Extend deliberately, without overstating what exists.

TOYTOCOL’s platform direction anticipates an ecosystem around its governed core. Every item below is a roadmap direction, not an operational service or current integration.

Roadmap

SDKs and developer contracts

Documented, bounded ways to build against stable platform capabilities.

Roadmap

Capability packs

Optional domain-focused capability bundles that remain separate from the base experience.

Roadmap

Connectors

Governed exchange with approved external sources and systems.

Roadmap

Certification

Quality and trust criteria for ecosystem contributions.

Roadmap

Federation

Controlled collaboration across independently governed environments.

Roadmap

Domain extensions

Purpose-built experiences that reuse the platform’s investigation and governance concepts.

Put the capabilities in motion

Follow a complete fictional investigation.

Aurora shows how evidence, competing hypotheses, a bounded Finding, human Verification, and retained limitations work together.

Try the Aurora demo