L6
NS-L6 STANDARD
Human–LLM Responsibility Framework
GOVERNANCE
Governance Model

The governance layer defines how the NS-L6 Standard is maintained, versioned, validated, and communicated. It ensures transparency, stability, and long-term structural integrity of the specification.

Read Framework Read RFC Layer

Governance model (v1.1)

For NS-L6 v1.1, the standard is governed under a deterministic editorial model. The original author acts as the canonical editor and custodian of the standard.

  • Single canonical editor (authorial governance).
  • All normative text is maintained in the canonical Git repository.
  • Changes must preserve structural and temporal determinism of the framework.
  • Non-normative material (informative notes, examples) may evolve faster.

Canonical Manifest Source:
github.com/jan-zdrahal/jan-zdrahal/tree/main/manifest

Status: FINAL — Normative governance layer
Aligned release: NS-L6 v1.1

Release process

NS-L6 uses a staged release process designed for transparency and auditability. Each public version is anchored, documented, and preserved.

  • Draft — internal validation, not for external conformance.
  • Candidate — structurally complete, under focused review.
  • Final — authoritative normative release.
  • Archived — frozen for citation and historical reference.

Versioning scheme: major.minor.patch (structural / normative / clarificatory).

Detailed governance structure

1. Governance purpose

The governance model provides the authoritative structure for maintaining the NS-L6 Standard. Its purpose is to guarantee:

  • predictability of normative requirements,
  • a clear separation of normative and informative content,
  • a stable and transparent release lifecycle,
  • traceability and authorship integrity.

2. Normative vs. informative content

The standard distinguishes between binding and non-binding material:

  • Normative — defines requirements, invariants, and rules.
  • Informative — provides explanation, rationale, examples.
  • Annexes — may be normative or informative; the status is explicitly marked.

3. Versioning model

NS-L6 version numbers follow a deterministic design:

  • Major (v1 → v2): structural changes to the framework or layers.
  • Minor (v1.1 → v1.2): normative expansions within the existing structure.
  • Patch (v1.1.1): clarifications without normative impact.

All past versions remain permanently available for citation and audit.

4. Release lifecycle

The release cycle uses four fixed phases:

  • Draft — internal validation only.
  • Candidate — completeness and consistency verification.
  • Final — normative, authoritative publication.
  • Archived — preserved as a frozen reference.

5. Authorship & traceability

The NS-L6 Standard is authored and curated by:

Jan Zdráhal (Author & Custodian of the Standard)

All official releases are cryptographically anchored, externally time-stamped, and permanently archived to ensure provenance and priority.

6. Conformance structure

Conformance has two axes:

  • Structural — responsibilities, invariants, mappings.
  • Procedural — lifecycle and operational integrity.

7. Independence & neutrality

The NS-L6 Standard is designed to be:

  • platform-neutral,
  • vendor-independent,
  • model-agnostic,
  • free of commercial influence.

Only content published at ns-l6.org is authoritative.

8. Public specification repository

All normative documents are archived at:

github.com/jan-zdrahal/ns-l6-standard

9. Future governance extensions

Future governance materials may include:

  • Formal change-control protocol (RFP/RFC model).
  • Register of normative interpretations.
  • Independent compliance verification.
  • Alignment with external legal and regulatory frameworks.