TENSOR Framework

TENSOR Standards and Conformance

TENSOR Core Standards Package v1.0.0

This package defines release and compatibility rules for multi-vendor interoperability. Core semantics remain consortium-managed; organization-specific behavior belongs in overlays.

Package Artifacts

Conformance Tier Matrix

Tier Scope Minimum Evidence
Consumer Read, validate, and surface graph/schema semantics. Pass valid fixture; reject invalid fixture with explicit reason.
Executor Execute branch traversal using deterministic decisions. Replayable traversal logs with node and edge IDs.
Authoring Tool Create compatible graph updates without breaking existing consumers. Schema-valid output plus ID stability across revisions.

Conformance Starter Suite

The starter suite provides deterministic baseline checks. Extend locally for domain needs, but preserve the core validation contract.

Release and Deprecation Policy

Change Type Version Rule Deprecation Expectation
Additive node/edge/category change Minor version increment Must not break existing compliant consumers.
Semantic change to existing IDs Major version increment Requires migration notes and deprecation window.
Schema constraint tightening Minor or major based on compatibility impact Must publish rationale and affected fixture updates.

FAQ

Is TENSOR a replacement for SIEM or SOAR platforms?

No. TENSOR is a shared investigation contract above those systems. It standardizes semantics, not vendor product features.

Can vendors innovate while staying compatible?

Yes. Core semantics remain stable while overlays and extensions carry differentiated behavior.

Where should we start?

Start with Implement Core, then run Conformance Suite before release.