wiki/projects/telic-field-papers/artifacts/hi-9-consentful-training

Rendered from markdown source. Open raw source on GitHub.

--- title: "Telic Fields HI-9 — Consentful Training, Source Standing, and Model Lineage" artifact_date: "2026-07-15" artifact_type: "paired-technical-and-public-pass" domain: "TELIC-FIELDS" scope: "WORKING" lineage: "THE-TELIC-FIELD-PAPERS" status: "working" processing_tier: 4 source_role: "derived-technical-and-public-architecture-artifact" content_canon_status: "unset" publication_status: "unpublished" series_position: "HI-9" ---

Telic Fields HI-9 — Consentful Training, Source Standing, and Model Lineage

Parent lineage: The Telic Field Papers

Source artifacts

I.9 technical branch

• I.9 consentful training, source standing, and model lineage specification
• Source standing, access, and transition authority matrix
• Annotation, preference, constitution, and synthetic ancestry matrix
• Withdrawal, unlearning, derivative propagation, and benefit matrix

H.9 public branch

• H.9 What the Model Learned From Us

Gate, validation, and export

• HI-9 gate review
• HI-9 validation report
• HI-9 negative conformance fixtures
• HI-9 validation results
• HI-9 validation runner
• HI-9 consentful-training witness export

Positive demonstrations and training-lineage records

• PD-1 public source not authorized for training
• PD-2 publication does not authorize deployment
• PD-3 preference data retains conditional provenance
• PD-4 constitution authority remains visible
• PD-5 synthetic ancestry survives transformation
• PD-6 withdrawal produces bounded unlearning
• PD-7 derivative models receive correction
• PD-8 benefit claim connected to contribution
• Training-lineage event stream
• Generated consentful-training witness
• Annotation and preference data record
• Benefit and contributor recognition record
• Collection authorization records
• Derivative correction propagation
• License, authority, and consent profile
• Model constitution lineage
• Preference optimization record
• Source and dataset standing records
• Synthetic-data ancestry record
• Training-transformation lineage
• Withdrawal and unlearning record

I.9 candidate schemas

The twelve candidate schema sources are preserved under the standard-named source directory, with the SCHEMA__CANDIDATE__I-9 prefix: source/dataset standing, collection authorization, license/authority/consent profile, training-transformation lineage, annotation/preference data, model constitution lineage, preference optimization, synthetic-data ancestry, withdrawal/unlearning, derivative correction propagation, benefit/contributor recognition, and consentful-training witness.

Intake archive

• Complete HI-9 intake package

Package SHA-256: d2045b96ecfe83b5b4373ea024270aba781e14854b4cad8b949f0b06691154b1

The complete package and its independent training-lineage witness export passed their internal SHA-256 manifests before installation. The standard-named copies are byte-preserving source copies; the inbound ZIP and extracted contents remain in the intake archive.

Working focus

HI-9 completes I.9 and H.9 as a phase-locked pass. It treats training as a recruitment relation; distinguishes public availability, access, permission, consent, ownership, and legitimacy; makes authority transition-specific; preserves source and community standing through transformation; retains annotation and preference provenance; exposes model constitutions; preserves synthetic ancestry; governs withdrawal and bounded unlearning; propagates obligations to derivative models; connects benefit sharing to contribution; and separates training legitimacy from deployment authority.

The package reports twelve candidate schemas, eight positive demonstrations, twelve negative conformance fixtures, an event-generated ConsentfulTrainingWitness, an independent training-lineage export, and zero technical/public contradictions. These are structural and internal semantic validations, not legal conclusions, complete provenance, exact machine unlearning, universal community authority, sufficient compensation, production security, scientific validity, or public-reader comprehension.

Gate and boundaries

HI-9 is complete at v0.1 with a PASS WITH CONDITIONS gate. Remaining conditions include incomplete provenance, community-authority capture, restriction loss through mixing, preference universalization, unlearning theater, successor opacity, benefit washing, and independent public-reader testing.

The I.9 specification, H.9 page, matrices, schemas, demonstrations, fixtures, and export remain working/candidate artifacts. Installation does not make them canonical or production specifications.

Roadmap transition

The next paired pass is HI-10:

• I.10 Consentful Deployment, Runtime Authority, and Model Succession Specification
• H.10 What the Model May Do With What It Learned

HI-10 should remain phase-locked through deployment-field assembly, affected-center standing, runtime authority, capability and tool grants, deployment consent, output capture, scope drift, incident repair, consequence return, operator/provider transfer, model succession, rollback, shutdown, and residual obligations.