@tiinex/app 0.1.1

package/src/tooling/portable/schema/fixtures/tiinex.transition.definition.v1.field-domain.contract-fixture.md

@@ -0,0 +1,319 @@
+<!-- Contract-only pressure fixture transcribed from the field-domain authority surface in Tiinex/docs@0194368549bbf3da4817bc47c2c6eb13b1791fee. Not a canonical snapshot. -->
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Parent
+  - Parent Schema: tiinex.root.v1
+  - Trace: root.trace.md
+  - Origin: root.trace.md
+- Current
+  - Current Schema: tiinex.transition.definition.v1
+  - Created At: 2026-08-16 00:00:00
+
+---
+
+# Transition Definition Field-Domain Contract Fixture
+
+## Schema Validation Contract
+
+### Input Role Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Meaning
+- Minimum Count
+- Maximum Count
+
+Optional Fields
+
+- Acquisition Policy
+- Target Kind
+- Schema Constraint
+
+Field Value Constraints
+
+- Acquisition Policy
+  - Allowed Value: existing-only
+  - Allowed Value: existing-or-create
+  - Allowed Value: create-only
+  - Allowed Value: invocation-provided
+  - Allowed Value: derived
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `## Input Roles` are repeated named declarations using this shape.
+
+### Output Role Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Meaning
+- Minimum Count
+- Maximum Count
+
+Optional Fields
+
+- Target Kind
+- Schema Constraint
+- Generation Binding
+
+Field Value Constraints
+
+- Generation Binding
+  - Allowed Value: target-schema
+  - Allowed Shape: Markdown Link
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `## Output Roles` are repeated named declarations using this shape.
+
+### Target Kind Semantics
+
+Applies To
+
+- Input Role Declaration
+- Output Role Declaration
+
+Field Value Constraints
+
+- Target Kind
+  - Allowed Value: artifact
+  - Allowed Value: non-artifact
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+### Lifecycle Effect Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Target Binding
+- Effect
+
+Optional Fields
+
+- Logical Continuity
+- Required Materialization Operation
+- Preserve Why
+- Member Mapping
+
+Field Value Constraints
+
+- Effect
+  - Allowed Value: create-new
+  - Allowed Value: revise-current
+  - Allowed Value: preserve
+  - Allowed Value: supersede
+  - Allowed Value: retire
+  - Allowed Value: domain-consume
+  - Allowed Value: remove-materialization
+  - Allowed Value: custom
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+- Logical Continuity
+  - Allowed Value: new-subject
+  - Allowed Value: preserve-subject
+  - Allowed Value: no-subject-effect
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+- Required Materialization Operation
+  - Allowed Value: create
+  - Allowed Value: revise
+  - Allowed Value: delete
+  - Allowed Value: move
+  - Allowed Value: tombstone
+  - Allowed Value: restore
+  - Domain Policy: extension-authorized
+
+- Preserve Why
+  - Allowed Value: yes
+  - Allowed Value: no
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `### Lifecycle Effects` are repeated lifecycle declarations using this shape.
+
+### Parent Effect Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Target Binding
+- Effect
+
+Optional Fields
+
+- Member Mapping
+
+Field Value Constraints
+
+- Effect
+  - Allowed Value: set
+  - Allowed Value: preserve
+  - Allowed Value: clear
+  - Allowed Value: replace
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+- Member Mapping
+  - Allowed Value: single
+  - Allowed Value: broadcast
+  - Allowed Value: pairwise
+  - Allowed Value: by-key
+  - Allowed Value: explicit-at-invocation
+  - Allowed Value: custom
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `### Parent Effects` are repeated Parent Effect declarations using this shape.
+
+### Relation Effect Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Effect
+- Subject Binding
+- Predicate Identifier
+- Predicate Meaning
+- Object Binding
+- Directionality
+
+Optional Fields
+
+- Member Mapping
+
+Field Value Constraints
+
+- Effect
+  - Allowed Value: declare
+  - Allowed Value: remove
+  - Allowed Value: preserve
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+- Directionality
+  - Allowed Value: directed
+  - Allowed Value: undirected
+  - Allowed Value: bidirectional
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `## Relation Effects` are repeated named declarations using this shape.
+
+### Member Mapping Semantics
+
+Applies To
+
+- Lifecycle Effect Declaration
+- Parent Effect Declaration
+- Relation Effect Declaration
+
+Field Value Constraints
+
+- Member Mapping
+  - Allowed Value: single
+  - Allowed Value: broadcast
+  - Allowed Value: pairwise
+  - Allowed Value: all-to-all
+  - Allowed Value: by-key
+  - Allowed Value: explicit-at-invocation
+  - Allowed Value: custom
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+### Destination Binding Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Meaning
+- Required
+
+Optional Fields
+
+- Destination Kind
+
+Field Value Constraints
+
+- Required
+  - Allowed Value: yes
+  - Allowed Value: no
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `### Destination Bindings` are named reusable destination slots using this shape.
+
+### Output Placement Declaration
+
+Entry Shape
+
+- First-Level Hyphen List Item
+
+Required Fields
+
+- Output Binding
+- Placement Intent
+
+Optional Fields
+
+- Naming Authority
+- Explicit Override Allowed
+
+Field Value Constraints
+
+- Placement Intent
+  - Allowed Value: preserve-current
+  - Allowed Value: new-materialization
+  - Allowed Value: no-materialization
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+- Naming Authority
+  - Allowed Value: target-schema
+  - Allowed Value: explicit-binding
+  - Allowed Value: external-authority
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+- Explicit Override Allowed
+  - Allowed Value: yes
+  - Allowed Value: no
+  - Allowed Value: unknown
+  - Domain Policy: closed
+
+Rules
+
+- Entries under `### Output Placements` are repeated Output Placement declarations using this shape.

package/src/transitions/canonical-schema-cache/053d46ce082d4ec261b82abc44ecca403d61e240/tiinex.relation.v1.schema.md

@@ -0,0 +1,240 @@
+# Continuity Context
+
+- Envelope Schema: [tiinex.root.v1](../tiinex.root.v1.schema.md)
+- Parent
+  - Parent Schema: [tiinex.root.v1](../tiinex.root.v1.schema.md)
+  - Created At: 2026-06-14 00:00:00
+  - Trace: [tiinex.root.v1.schema.md](../tiinex.root.v1.schema.md)
+  - Origin:
+    - [relative](../tiinex.root.v1.schema.md)
+    - [browse + git](https://github.com/Tiinex/docs/blob/2f5c1eea03aad31a0209f0484e17d2cc37d92dab/.topics/.schemas/tiinex.root.v1.schema.md)
+- Current
+  - Current Schema: [tiinex.relation.v1](tiinex.relation.v1.schema.md)
+  - Created At: 2026-06-26 00:00:00
+  - Summary: Schema for typed non-parent relations between artifacts, targets, inputs, contributors, or domain entities.
+
+---
+
+# Relation
+
+- Status: maintained schema note
+
+## Summary
+
+This schema defines typed relationship artifacts for Tiinex references that are
+not direct artifact-continuity parents. Ordinary artifacts and schemas may also
+declare or project typed relation edges without creating a Relation Artifact.
+
+It exists to keep `Parent` narrow while still allowing descendant schemas and
+runtime surfaces to express domain relationships such as contributors, inputs,
+subjects, verifiers, samples, datasets, dependencies, or candidate sources.
+
+## Schema Validation Contract
+
+### Relation Scope
+
+Applies To
+
+- artifacts whose `Current -> Current Schema` is `tiinex.relation.v1`
+
+Rules
+
+- `tiinex.relation.v1` identifies artifacts whose main job is to declare one or more typed non-parent relationships.
+- A typed relation does not require a standalone Relation Artifact merely to exist; ordinary artifacts or schema contracts may declare or project typed edges when another artifact owns the main semantics.
+- Use a Relation Artifact when the relation instance itself has independent semantic content, provenance, state, interpretation limits, or lifecycle worth preserving as an artifact.
+- A relation artifact must not reinterpret `Parent` as a generic graph edge.
+- A relation artifact may describe domain, runtime, validation, evidence, biological, legal, or data relationships without making those targets direct continuity parents.
+- Prose outside `Schema Validation Contract` may explain the schema, but it does not add required validation rules.
+
+### Relation Body
+
+Required Shape
+
+- first body heading after the continuity envelope
+- `## Relation Declaration` section
+- `## Relation Target` section
+- `## Relation Boundary` section
+
+Optional Sections
+
+- Relation Source
+- Evidence Basis
+- Interpretation Limits
+- Related Artifacts
+- Domain Mapping
+- References
+
+Rules
+
+- A relation artifact should begin with a human-readable title.
+- `Relation Declaration` must name the relation type and direction in readable form.
+- `Relation Target` must identify the related artifact, external target, or bounded target descriptor.
+- `Relation Boundary` must state that the relation is not a Tiinex `Parent` unless it is separately declared in the continuity envelope.
+- Domain-specific descendants may add stricter local relation fields and vocabularies.
+
+### Relation Declaration
+
+Required Fields
+
+- Relation Type
+- Relation Direction
+- Relation Scope
+
+Optional Fields
+
+- Relation Family
+- Relation Strength
+- Confidence
+- Domain Vocabulary
+- Valid From
+- Valid Until
+
+Rules
+
+- `Relation Type` should be specific enough that a later reader can distinguish contributor, input, target, subject, verifier, dependency, sample source, or other local semantics.
+- `Relation Direction` should state how the current artifact relates to the target.
+- `Relation Scope` should state whether the relation is artifact-level, body-level, claim-level, runtime-level, domain-level, or another bounded scope.
+- A relation declaration must not use vague labels such as `related` when a more specific relation type is known.
+- A relation declaration may preserve uncertainty through `Confidence` or `Interpretation Limits` instead of inventing certainty.
+
+### Relation Target
+
+Allowed Shapes
+
+- markdown link to a Tiinex artifact
+- relative path to a Tiinex artifact
+- external URL
+- external descriptor
+- evidence artifact reference
+- payload reference
+- bounded textual target description
+
+Rules
+
+- A relation target should be as durable and recoverable as the available context allows.
+- A relation target may be non-traversable when the related material is external, private, missing, or intentionally described rather than linked.
+- When a relation target is a Tiinex artifact, a commit-pinned `browse + git` target should be preferred when available for durable recovery.
+- Multiple relation targets are allowed only when the body keeps each target and its relation type distinguishable.
+- When multiple relation targets are present, each target must be associated with a distinguishable `Relation Type`, `Relation Direction`, and `Relation Scope`, either through separate grouped entries or explicit target-local fields.
+
+### Relation Boundary
+
+Rules
+
+- `Parent` remains direct artifact-continuity ancestry.
+- A relation target is not a parent merely because it influenced, contributed to, verified, described, sampled, or constrained the current artifact.
+- Multi-input domain reality should be modeled through relation semantics, not through multiple `Parent` entries.
+- Descendant schemas must not weaken the inherited root rule that `Parent` describes ancestry only.
+
+### File Naming
+
+Allowed Shapes
+
+- `<lineage>.trace.md`
+- `<lineage>-relation.trace.md`
+- `<lineage>-<relation-slug>.trace.md`
+
+Rules
+
+- Relation artifacts should keep the lineage label first.
+- The optional slug should identify the relation or target family rather than a low-signal implementation detail.
+- Relation artifacts should keep the `.trace.md` suffix stable.
+
+### Interpretation Boundaries
+
+Rules
+
+- Use `tiinex.relation.v1` when the main artifact value is an explicit typed non-parent relation.
+- Do not create a Relation Artifact as a mandatory intermediate node for every meaningful graph edge.
+- When another artifact owns the main semantics, that artifact may project a typed relation directly if its active contract preserves the predicate/target meaning.
+- Do not use `tiinex.relation.v1` to replace evidence, decision, feedback, task, topic, pointer, or runtime schemas when those schemas own the main artifact role.
+- Do not use `tiinex.relation.v1` for direct continuity ancestry; use the root `Parent` envelope when direct continuity is being declared.
+
+## Minimal Example
+
+```md
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.relation.v1
+  - Created At: 2026-06-26 00:00:00
+  - Summary: Biological contributor relation for a genetic analysis artifact.
+
+---
+
+# Biological Contributor Relation
+
+## Relation Declaration
+
+- Relation Type: biological contributor
+- Relation Direction: current analysis -> contributor artifact
+- Relation Scope: domain-level genetic interpretation
+- Confidence: partial
+
+## Relation Target
+
+- Target: maternal-sample-artifact.trace.md
+
+## Relation Boundary
+
+- This target is a biological contributor, not the Tiinex continuity parent of this artifact.
+```
+
+A multi-target relation should keep target-local semantics distinguishable:
+
+```md
+# Genetic Contributor Relation Bundle
+
+## Relation Declaration
+
+- Relation Type: biological contributor
+- Relation Direction: current analysis -> contributor artifacts
+- Relation Scope: domain-level genetic interpretation
+- Confidence: partial
+
+## Relation Target
+
+- Target: maternal-sample-artifact.trace.md
+  - Relation Type: maternal biological contributor
+  - Relation Direction: current analysis -> maternal contributor artifact
+  - Relation Scope: domain-level genetic interpretation
+- Target: paternal-sample-artifact.trace.md
+  - Relation Type: paternal biological contributor
+  - Relation Direction: current analysis -> paternal contributor artifact
+  - Relation Scope: domain-level genetic interpretation
+
+## Relation Boundary
+
+- These targets are biological contributors, not Tiinex continuity parents of this artifact.
+```
+
+## Validation-Friendly Shape
+
+Keep this schema note in the exact section order already used here:
+`Summary`, `Schema Validation Contract`, `Minimal Example`,
+`Validation-Friendly Shape`, and `Interpretation Notes`.
+
+Maintain the section headings exactly in this schema note. Free markdown inside
+those sections is allowed, but adding undeclared new section headings should be
+treated as schema drift.
+
+## Interpretation Notes
+
+- relation artifacts preserve non-parent relationships without weakening root continuity
+- relation targets may be many, but `Parent` remains singular when present
+- domain schemas should prefer extending relation semantics over inventing local parent-like fields
+- `subject` may be modeled as a relation type unless a later dedicated subject schema becomes necessary
+- this support/governance schema intentionally omits `Artifact Creation Contract` until ordinary app creation behavior is explicitly declared
+
+---
+
+# Continuity Integrity
+
+- sha256-base64url-c14n-v1
+  - Towards: [tiinex.root.v1.schema.md](https://github.com/Tiinex/docs/blob/2f5c1eea03aad31a0209f0484e17d2cc37d92dab/.topics/.schemas/tiinex.root.v1.schema.md)
+  - Value: 3pgzWX3ICCeChCyP6dLAc6VCYBpVBHy7BtbVU-QU8PA
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: Xvbb4_ekLH_HFWU34MXmYLCIY_BYjpPIqynbSblTcNs