Skip to content

SKC Quickstart

This guide introduces the minimum SKC workflow without assuming a stable public CLI contract.

Start with structured knowledge, derive a semantic core, reconstruct the knowledge state and validate the result.

Example:

{
"entities": [
{ "id": "system", "type": "software" },
{ "id": "artifact", "type": "evidence" }
],
"relations": [
{
"from": "system",
"type": "produces",
"to": "artifact"
}
]
}

SKC requires explicit objects and relations before canonical state can be reasoned about deterministically.

Conceptually:

Raw Input
↓
Normalize
↓
Semantic Graph

Equivalent semantic inputs should converge toward the same canonical representation where the contract defines them as equivalent.

Semantic Graph
↓
Canonicalization
↓
Canonical Semantic State

The semantic core should preserve the minimum structure required for successful reconstruction under the defined SKC contract.

Canonical State
↓
Compression
↓
Semantic Core
Semantic Core
↓
Reconstruction
↓
Reconstructed State

A successful SKC experiment should not report only a size reduction.

It should also measure reconstruction and structural equivalence.

Important metrics include:

  • BlueprintSize
  • SemanticCoreSize
  • ReductionRatio
  • CompressionRatio
  • ReconstructionFidelity
  • GraphEquivalence
  • SemanticEntropy
  • Deterministic

Continue with SKC Architecture →.