01 / TECHNICAL RELEASE
↗Codebase onboarding 1.1.0
Trace a product journey, C1/C2 views, and file evidence before changing code.
NKSKILLS / CATALOG
The skills behind the workflow.
NKSkills has two layers: Solution Skills define the outcome and sequence; Upstream Skills provide selected capabilities with pinned versions and recorded sources.
01 / SOLUTION SKILLS
Workflows packaged around an outcome.
Each Solution Skill has its own version, component manifest, and verification criteria. These statuses reflect current evidence.
02 / EVALUATION CANDIDATE
↗Problem presentation 0.1.0
Create an offline HTML and PDF deck around one evidenced problem and decision. Commercial release gate remains open.
02 / UPSTREAM SKILLS
Public sources, precise revisions.
This catalog tracks source, commit, and license. Some skills help author this website; listing one here does not make it part of a released Solution Skill.
hallmarkTracked source
designdocumentation
MIT
↗13ac0ec7e1html-slides-referenceTracked source
presentationslides
MIT
↗9c4c7d5cd2archifyTracked source
diagramsarchitecture
MIT
↗88d1ae4498diagram-designTracked source
diagramsdesign
MIT
↗550fd66edfvisual-explainerTracked source
presentationslides
MIT
↗5a1b3c4d6efrontend-designAuthoring tool
designfrontend
Apache-2.0
↗dbd4588f9ecopywritingAuthoring tool
marketingcopywriting
MIT
↗365b412152Source: repository catalog.yaml. Full commits, checksums, attribution, and local modifications are recorded there. catalog.yaml ↗
03 / VERSIONING
Updates, with a review step.
We monitor upstream commits. A new commit becomes a candidate for license, content, and impact review. A Solution Skill changes only through its own versioned manifest and fresh verification evidence.
Read the product model →