Public implementation candidate · 0.1.0-draft.1
Carry the investigation, including its reasoning
TENSOR Core proposes a shared contract for cyber investigations. A portable record connects questions, evidence references, observations, hypotheses, assessments, decisions, and recorded actions. Humans and agents use the same meanings and attribution rules.
This candidate adds an investigation record to TENSOR's question-graph foundation. The existing question release remains preserved and separately versioned. Core 0.1.0-draft.1 is available for implementation and review; it is not a ratified standard.
Try Investigation Lab Implement the candidate
One shared layer, many implementations
- Products and servicesInvestigator interfaces, agent runtimes, evidence stores, integrations, and business workflows.
- Public profiles and extensionsDomain-specific questions and explicit additional semantics, with declared compatibility requirements.
- TENSOR CorePortable meaning, identity, context, provenance, revision history, and exchange rules.
Vendor and business layers can build above Core. They must declare additional meaning and preserve the shared record. An agent identity or an imported action record does not grant authority to perform an action.
Read and download the contract
Purpose and normative proposal
Executable candidate binding
The founding contract states proposed meaning and behavior. The versioned binding makes those rules concrete for an implementation candidate. Check both when interpreting a result; a schema-valid object alone does not establish semantic validity.
Two synthetic reference investigations
- AI-system investigation bundle: inspect an agent-related case and its recorded reasoning.
- Identity investigation bundle: inspect the same Core concepts in a conventional cyber investigation.
Each bundle includes a record and the exact definition bytes used by its digest pins. Use the Lab to inspect, validate, export, and reimport it. These are examples, not real incident evidence.
What a validation result means
The reference validator checks the candidate's supported structural and semantic requirements. It reports failures and unsupported required meaning explicitly. A valid unknown assessment is different from an indeterminate validation result.
Validation does not establish evidence truth, investigative completeness, legal authority, or operational safety. The validator does not retrieve evidence or execute recorded actions. Read the reporting rules before making an implementation claim.
Help move the candidate forward
The next evidence is an exchange between separately developed implementations, useful investigator feedback, and public resolution of open design questions. The acceptance scenarios, review plan, and decision register make that work reviewable.
Contribute a case, review, or implementation report · How TENSOR relates to existing standards