Skip to content

docs(internal): v4.2 internal target skill mapping (draft, not a public release)#119

Merged
1 commit merged into
mainfrom
docs/internal-skill-v42-mapping
Jun 2, 2026
Merged

docs(internal): v4.2 internal target skill mapping (draft, not a public release)#119
1 commit merged into
mainfrom
docs/internal-skill-v42-mapping

Conversation

@Davincc77
Copy link
Copy Markdown
Owner

Summary

Adds internal-only documentation for the xklickd_internal_skill_v4_2 target mapping, ahead of internal production. Two new files under a new docs/internal/ directory:

  • docs/internal/INTERNAL_SKILL_V4_2_MAPPING.md — the v4.2 internal target skill mapping.
  • docs/internal/README.md — scope marker for the directory.

This is not a public release. It is non-normative planning material, comparable to docs/chimera/ but scoped to the internal track.

What the mapping captures (validated corrections)

  • Governance symmetrygovernance_system is documented in the same detail as memory_system (authority_hierarchy, human_veto, consent_rules, risk_levels, action_gates, non_lowerable_rules, escalation_rules, approval_lifecycle, revocation_rules, policy_conflict_resolution, governance_audit).
  • supply_chainskill_lifecycle — renamed conceptually; the doc explicitly does not claim supply-chain completeness.
  • output_contract.graph_bindings — output contract wired to context_graph (creates_action_node, requires_policy_node, requires_evidence_node, may_trigger_veto_edge, writes_audit_edge).
  • Naming harmonisationdomain_primaryprimary_domain_competencies, domain_secondarysecondary_domain_competencies, domain_risk_modeldomain_risk_profile, domain_output_contractdomain_output_requirements, plus competency_core.
  • interactions layer + canonical flow — a new top-level layer documenting directed flows between layers, with the canonical end-to-end task flow.

Boundaries / non-claims

  • Public .klickd stays v4.0.0 GA; the 42 x.klickd artefacts remain v4.1 candidates. No public v4.2 release is claimed.
  • No tag, DOI, npm/PyPI latest, GitHub Release, schema, SDK, vector, or lock-file change.
  • No examples/v4.1/x-klickd-skills/ artefact modified; no public README / CHANGELOG / Zenodo / CITATION change.
  • Internal track name xklickd_internal_skill_v4_2 kept out of all public-facing surfaces (verified: name appears only under docs/internal/).
  • Scoped to Davincc77/klickdskill only; no other repository referenced or touched.

Testing

  • git diff --cached --name-status main → only the two new docs/internal/ files added.
  • Forbidden-claim grep (released / GA / public v4.2 / tagged / DOI) → only disclaimer/negation sentences match; no actual claim.
  • Internal-name leakage grep → name present only under docs/internal/.
  • python3 scripts/validate_v4_1_candidate_mapping.py → PASS (42 artefacts validated).
  • python3 scripts/validate_v4_schemas.py → all v4 strict-schema validations passed.
  • Public version files unchanged: package.json, .zenodo.json, CITATION.cff all still 4.0.0; v4.1 artefact count unchanged (8 lite + 34 pro = 42).

🤖 Generated with Claude Code

…blic)

Internal documentation only, ahead of internal production. Adds
docs/internal/INTERNAL_SKILL_V4_2_MAPPING.md + README capturing the
validated v4.2 mapping corrections:

- governance_system detailed and symmetric with memory_system
- supply_chain renamed conceptually to skill_lifecycle (no completeness claim)
- output_contract wired to context_graph via graph_bindings
- harmonised competency/domain naming (primary/secondary_domain_competencies,
  domain_risk_profile, domain_output_requirements, competency_core)
- explicit interactions layer + canonical end-to-end flow

Non-normative, no release. Public .klickd stays v4.0.0 GA; the 42 x.klickd
artefacts remain v4.1 candidates. No tag/DOI/package/schema/SDK change, no
public v4.2 claim, no artefact modified. Internal track name kept out of
public surfaces.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Davincc77 Davincc77 closed this pull request by merging all changes into main in 47d244c Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant