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.
1. Start with explicit source knowledge
Section titled “1. Start with explicit source knowledge”Example:
{ "entities": [ { "id": "system", "type": "software" }, { "id": "artifact", "type": "evidence" } ], "relations": [ { "from": "system", "type": "produces", "to": "artifact" } ]}2. Normalize semantic structure
Section titled “2. Normalize semantic structure”SKC requires explicit objects and relations before canonical state can be reasoned about deterministically.
Conceptually:
Raw Input ↓Normalize ↓Semantic Graph3. Derive a canonical semantic state
Section titled “3. Derive a canonical semantic state”Equivalent semantic inputs should converge toward the same canonical representation where the contract defines them as equivalent.
Semantic Graph ↓Canonicalization ↓Canonical Semantic State4. Reduce to a semantic core
Section titled “4. Reduce to a semantic core”The semantic core should preserve the minimum structure required for successful reconstruction under the defined SKC contract.
Canonical State ↓Compression ↓Semantic Core5. Reconstruct
Section titled “5. Reconstruct”Semantic Core ↓Reconstruction ↓Reconstructed State6. Validate
Section titled “6. Validate”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 →.