@tiinex/app 0.1.1

package/src/schemas/coordination/project/tiinex.project.v1.schema.md

@@ -0,0 +1,311 @@
+# 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/089427470f04336dfcc100c4dcf6289d51bf0291/.topics/.schemas/tiinex.root.v1.schema.md)
+- Current
+  - Current Schema: [tiinex.project.v1](tiinex.project.v1.schema.md)
+  - Created At: 2026-06-30 00:00:00
+  - Summary: Schema for a bounded coordinated effort over time with purpose, scope, parties, resources, tasks, events, milestones, decisions, risks, and outcomes without making one project methodology the base concept.
+
+---
+
+# Project
+
+- Status: draft schema note
+
+## Summary
+
+Schema for a bounded coordinated effort over time with purpose, scope, parties, resources, tasks, events, milestones, decisions, risks, and outcomes without making one project methodology the base concept.
+
+This schema is human-first. It should be readable by a person who knows the parent schema but does not know a specialized app, programming language, management tool, calendar tool, or database.
+
+## Schema Validation Contract
+
+### Project Scope
+
+Applies To
+
+- artifacts whose `Current -> Current Schema` is `tiinex.project.v1`
+
+Rules
+
+- `tiinex.project.v1` identifies artifacts whose main job is to preserve project semantics.
+- A project artifact should state its identity, boundary, state, related targets, and interpretation limits in human-readable form.
+- A project artifact must not silently become proof, consent, authority, attendance, allocation, validation, or truth unless those claims are separately supported by the appropriate schema or method.
+- Prose outside `Schema Validation Contract` may explain the schema, but it does not add required validation rules.
+
+### Project Body
+
+Required Shape
+
+- first body heading after the continuity envelope
+- `## Project Identity` section
+- `## Project Purpose And Scope` section
+- `## Parties And Resources` section
+- `## Coordination State` section
+- `## Milestones And Outcomes` section
+- `## Interpretation Limits` section
+
+Optional Sections
+
+- Related Artifacts
+- References
+
+Rules
+
+- A project artifact should begin with a human-readable title.
+- Required sections should be readable without specialized tooling.
+- Required sections should be structured enough that a reader, tool, or LLM can extract boundaries without guessing.
+- Follow-up sections must not replace the declared boundary and interpretation limits.
+### Project Identity
+
+Required Fields
+
+- Description
+- Boundary
+
+Optional Fields
+
+- Related Party
+- Related Resource
+- Related Event
+- Related Task
+- Related Project
+- Evidence Basis
+
+Rules
+
+- `Project Identity` must remain human-readable and bounded.
+- `Project Identity` must state what is known, what is unknown, and what must not be inferred when those limits matter.
+- `Project Identity` may reference relation, evidence, attestation, validation, privacy, source, access, resource, party, event, project, or instrument artifacts when those artifacts own companion semantics.
+
+### Project Purpose And Scope
+
+Required Fields
+
+- Description
+- Boundary
+
+Optional Fields
+
+- Related Party
+- Related Resource
+- Related Event
+- Related Task
+- Related Project
+- Evidence Basis
+
+Rules
+
+- `Project Purpose And Scope` must remain human-readable and bounded.
+- `Project Purpose And Scope` must state what is known, what is unknown, and what must not be inferred when those limits matter.
+- `Project Purpose And Scope` may reference relation, evidence, attestation, validation, privacy, source, access, resource, party, event, project, or instrument artifacts when those artifacts own companion semantics.
+
+### Parties And Resources
+
+Required Fields
+
+- Relevant Parties
+- Relevant Resources
+
+Optional Fields
+
+- Roles
+- Teams
+- Organizations
+- Facilities
+- Tools
+- Sources
+
+Rules
+
+- `Parties And Resources` must remain human-readable and bounded.
+- `Parties And Resources` must state what is known, what is unknown, and what must not be inferred when those limits matter.
+- `Parties And Resources` may reference relation, evidence, attestation, validation, privacy, source, access, resource, party, event, project, or instrument artifacts when those artifacts own companion semantics.
+
+### Coordination State
+
+Required Fields
+
+- Description
+- Boundary
+
+Optional Fields
+
+- Related Party
+- Related Resource
+- Related Event
+- Related Task
+- Related Project
+- Evidence Basis
+
+Rules
+
+- `Coordination State` must remain human-readable and bounded.
+- `Coordination State` must state what is known, what is unknown, and what must not be inferred when those limits matter.
+- `Coordination State` may reference relation, evidence, attestation, validation, privacy, source, access, resource, party, event, project, or instrument artifacts when those artifacts own companion semantics.
+
+### Milestones And Outcomes
+
+Required Fields
+
+- Description
+- Boundary
+
+Optional Fields
+
+- Related Party
+- Related Resource
+- Related Event
+- Related Task
+- Related Project
+- Evidence Basis
+
+Rules
+
+- `Milestones And Outcomes` must remain human-readable and bounded.
+- `Milestones And Outcomes` must state what is known, what is unknown, and what must not be inferred when those limits matter.
+- `Milestones And Outcomes` may reference relation, evidence, attestation, validation, privacy, source, access, resource, party, event, project, or instrument artifacts when those artifacts own companion semantics.
+
+### Interpretation Limits
+
+Required Fields
+
+- Does Not Prove
+- Must Not Be Treated As
+
+Optional Fields
+
+- Open Questions
+- Review Needed
+
+Rules
+
+- `Interpretation Limits` must remain human-readable and bounded.
+- `Interpretation Limits` must state what is known, what is unknown, and what must not be inferred when those limits matter.
+- `Interpretation Limits` may reference relation, evidence, attestation, validation, privacy, source, access, resource, party, event, project, or instrument artifacts when those artifacts own companion semantics.
+
+### Allowed Or Common Shapes
+
+Allowed Shapes
+
+- coordinated effort
+- internal project
+- public project
+- research project
+- field project
+- documentation project
+- implementation project
+
+Rules
+
+- Allowed shapes are guidance for common reading and grouping, not an exhaustive vocabulary.
+- Local artifacts may use another precise human-readable shape when the declared boundaries remain clear.
+
+### File Naming
+
+Allowed Shapes
+
+- `<lineage>.trace.md`
+- `<lineage>-project.trace.md`
+- `<lineage>-<project-slug>.trace.md`
+
+Rules
+
+- Artifacts should keep the lineage label first.
+- The optional slug should describe the bounded artifact role rather than a low-signal implementation detail.
+- Ordinary lineage artifacts should keep the `.trace.md` suffix stable.
+
+### Interpretation Boundaries
+
+Rules
+
+- Use `tiinex.project.v1` when the main artifact value is the declared project role.
+- Do not use `tiinex.project.v1` to replace evidence, attestation, validation, consent, relation, task, decision, event, party, resource, or instrument artifacts when those schemas own the main role.
+- Parent remains direct continuity ancestry; related targets should be represented through relation or target fields unless direct continuation is being declared.
+
+## Artifact Creation Contract
+
+### Creation Fields
+
+Required Fields
+
+- Description
+- Boundary
+- Relevant Parties
+- Relevant Resources
+- Does Not Prove
+- Must Not Be Treated As
+
+### Creation Rules
+
+Rules
+
+- Creation tools should keep the artifact human-readable and bounded.
+- Creation tools should preserve unknown, partial, contested, private, unsafe, unavailable, or ambiguous state instead of inventing certainty.
+## Minimal Example
+
+```md
+# Project Example
+
+## Project Identity
+
+- Description: bounded example for tiinex.project.v1
+- Boundary: bounded example for tiinex.project.v1
+
+## Project Purpose And Scope
+
+- Description: bounded example for tiinex.project.v1
+- Boundary: bounded example for tiinex.project.v1
+
+## Parties And Resources
+
+- Relevant Parties: example project party or role
+- Relevant Resources: example resource or bounded descriptor
+
+## Coordination State
+
+- Description: bounded example for tiinex.project.v1
+- Boundary: bounded example for tiinex.project.v1
+
+## Milestones And Outcomes
+
+- Description: bounded example for tiinex.project.v1
+- Boundary: bounded example for tiinex.project.v1
+
+## Interpretation Limits
+
+- Does Not Prove: truth, consent, authority, attendance, allocation, or final outcome by itself
+- Must Not Be Treated As: tiinex.project.v1 example must not be treated as proof outside its declared boundary
+```
+
+## Validation-Friendly Shape
+
+Keep this schema note in the exact section order already used here: `Summary`, `Schema Validation Contract`, `Artifact Creation 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.
+
+The body headings required for artifacts using this schema are: `## Project Identity`, `## Project Purpose And Scope`, `## Parties And Resources`, `## Coordination State`, `## Milestones And Outcomes`, `## Interpretation Limits`.
+
+## Interpretation Notes
+
+- project is coordinated work over time, not a project methodology
+- project is not merely a large task or task board
+
+---
+
+# Continuity Integrity
+
+- sha256-base64url-c14n-v1
+  - Towards: [tiinex.root.v1.schema.md](https://github.com/Tiinex/docs/blob/089427470f04336dfcc100c4dcf6289d51bf0291/.topics/.schemas/tiinex.root.v1.schema.md)
+  - Value: BFWYft1v0Ue0gUoO236DGScvnixS7_MIEwO6mhJhkNw
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: Uwp3zgWt3BFj_bOupL2Fhn2GM1kQ5_KaoAFJKA-xGbw

package/src/schemas/core/decision/tiinex.decision.v1.schema.md

@@ -0,0 +1,227 @@
+# 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/089427470f04336dfcc100c4dcf6289d51bf0291/.topics/.schemas/tiinex.root.v1.schema.md)
+- Current
+  - Current Schema: [tiinex.decision.v1](tiinex.decision.v1.schema.md)
+  - Created At: 2026-06-05 01:00:00
+  - Summary: Schema for landed decision artifacts that state what now governs.
+
+---
+
+# Decision
+
+- Status: maintained schema note
+
+## Summary
+
+This schema defines artifacts whose main job is to record a landed decision in
+a way that later readers, traces, and tools can treat as operative.
+
+It is for artifacts where the main value is no longer broad exploration or
+execution planning, but what has now been decided and what follows from that.
+
+## Schema Validation Contract
+
+### Decision Scope
+
+Applies To
+
+- artifacts whose `Current -> Current Schema` is `tiinex.decision.v1`
+
+Rules
+
+- `tiinex.decision.v1` identifies artifacts centered on a landed or explicitly stated decision state.
+- The body should make the operative decision legible without requiring special tooling.
+- A decision artifact should tell a later reader what now governs, not just what was discussed.
+- Prose outside `Schema Validation Contract` may explain the schema, but it does not add required validation rules.
+
+### Decision Body
+
+Required Shape
+
+- first body heading after the continuity envelope
+- readable prose or lists that state the decision and what it applies to
+
+Optional Sections
+
+- Basis
+- Consequences
+- Review Conditions
+- Immediate Next Questions
+- Alternatives Considered
+- Supersession
+
+Rules
+
+- A decision artifact should begin with a human-readable title.
+- A decision artifact should contain enough body content that a later reader can identify the decision itself.
+- The body should make the subject or affected scope readable rather than leaving the reader to infer it from sparse metadata.
+- Follow-up sections must not replace the decision statement itself.
+- If the artifact is still mostly open-ended reasoning, another schema should own it instead.
+
+### Decision Semantics
+
+Allowed Shapes
+
+- accepted decision
+- rejected decision
+- deferred decision
+- superseded decision
+- provisional decision with explicit review conditions
+
+Rules
+
+- A decision artifact should make the current decision state explicit.
+- A decision artifact should make clear what was decided, rejected, deferred, or superseded.
+- If the decision is provisional, reversible, or pending later review, the artifact should say so explicitly.
+- If the decision authorizes later work or execution, the artifact should say that operative effect explicitly.
+- Decision artifacts should optimize for the landed outcome rather than replaying every branch of prior discussion.
+
+### Decision Envelope Companions
+
+Optional Fields
+
+- `Current -> Why`
+- `Current -> Summary`
+- `Current -> Authors`
+
+Rules
+
+- Decision artifacts may carry light current-side metadata when it helps a reader orient quickly.
+- Decision artifacts should declare parent signal when they continue, refine, or supersede an earlier local artifact.
+- Decision artifacts should avoid turning envelope metadata into the only decision-bearing surface.
+
+### File Naming
+
+Allowed Shapes
+
+- `<lineage>.trace.md`
+- `<lineage>-<decision-slug>.trace.md`
+
+Rules
+
+- Decision artifacts should keep the lineage label first.
+- The optional slug should describe the landed decision or affected scope.
+- Decision artifacts should prefer short human-readable slugs.
+- Decision artifacts should keep the `.trace.md` suffix stable.
+
+### Interpretation Boundaries
+
+Rules
+
+- Use `tiinex.decision.v1` when the artifact is mainly preserving a landed or explicitly stated decision state.
+- Do not use `tiinex.decision.v1` for broad exploration without a stated outcome.
+- Do not use `tiinex.decision.v1` for generic task execution or passive evidence capture.
+- If the artifact's main job is to preserve supporting material, another schema should own it.
+
+## Minimal Example
+
+```md
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.decision.v1
+  - Created At: 2026-06-05 00:00:00
+  - Summary: Decision to keep lineage repair audit and repair as separate surfaces.
+
+---
+
+# Audit And Repair Separation Decision
+
+## Decision
+
+- State: accepted
+- Subject: schema-lineage repair workflow shape
+- Decision: audit and repair remain separate surfaces for the current version
+
+## Basis
+
+- one blended surface would make it harder to tell whether the tool is diagnosing or mutating
+
+## Consequences
+
+- future planning should preserve explicit operator review before repair
+```
+
+## Validation-Friendly Shape
+
+Keep this maintained schema note in the exact section order already used here:
+`Summary`, `Schema Validation Contract`, `Minimal Example`,
+`Validation-Friendly Shape`, `Interpretation Notes`, and
+`Artifact Creation Contract`.
+
+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
+
+- a decision artifact should optimize for what now governs rather than for replaying all surrounding discussion
+- `Current -> Why` can help explain rationale, but it should not replace the body-level decision signal
+- if the artifact remains mostly open reasoning, a topic schema may be a better fit
+- if the artifact is mostly about work to be done after the decision, a task schema may be a better fit for that follow-on work
+
+## Artifact Creation Contract
+
+### Prompt Fields
+
+Required Fields
+
+- version
+- createTitle
+- summaryPrompt
+- summaryPlaceholder
+
+Optional Fields
+
+- whyPrompt
+- whyPlaceholder
+
+Rules
+
+- The current decision create surface uses version `1`.
+- `createTitle` should label the create action as `Create Decision`.
+- `summaryPrompt` should ask for the decision title.
+- `summaryPlaceholder` should guide the user toward the landed outcome.
+- `whyPrompt` and `whyPlaceholder` may be omitted when create flow does not ask for a why field.
+
+### Template Body
+
+Required Shape
+
+- first heading uses `# {{summary}}`
+- non-empty unheaded prose block after the first body heading and before the first second-level section
+- `## Decision` section
+- `## Basis` section
+- `## Consequences` section
+
+Rules
+
+- Generated decision artifacts should begin with the decision title as the first body heading.
+- The generated body must include one non-empty unheaded prose block after the first body heading and before the first second-level section.
+- That prose block may contain one or more human-readable sentences and may be authored content or placeholder guidance; exact lexical wording is not contract authority.
+- `Decision` should state the operative outcome and decision state.
+- `Basis` should explain why that outcome was chosen.
+- `Consequences` should state what now follows from the decision.
+- `Review Conditions` and `Immediate Next Questions` may be added when the generated artifact needs them.
+- Tools should preserve the same generated body shape even when they use a maintained built-in template.
+
+---
+
+# Continuity Integrity
+
+- sha256-base64url-c14n-v1
+  - Towards: [tiinex.root.v1.schema.md](https://github.com/Tiinex/docs/blob/089427470f04336dfcc100c4dcf6289d51bf0291/.topics/.schemas/tiinex.root.v1.schema.md)
+  - Value: BFWYft1v0Ue0gUoO236DGScvnixS7_MIEwO6mhJhkNw
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: HbQgKciHQObim8yJ3Xi5qWOMprTq3_Hq9BDKYYoVvm0