@tiinex/app 0.1.1

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

@@ -0,0 +1,229 @@
+# 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/00adbcc5b0319410cf16752a54dcbf4813173040/.topics/.schemas/tiinex.root.v1.schema.md)
+- Current
+  - Current Schema: [tiinex.task.v1](tiinex.task.v1.schema.md)
+  - Created At: 2026-06-05 02:00:00
+  - Summary: Schema for bounded task artifacts that define concrete work and completion.
+
+---
+
+# Task
+
+- Status: maintained schema note
+
+## Summary
+
+This schema defines artifacts whose main job is to state one bounded unit of
+work clearly enough to execute, review, or hand off.
+
+It is for concrete work slices where the reader should be able to tell what is
+being asked for, what completion means, and what boundaries still apply.
+
+## Schema Validation Contract
+
+### Task Scope
+
+Applies To
+
+- artifacts whose `Current -> Current Schema` is `tiinex.task.v1`
+
+Rules
+
+- `tiinex.task.v1` identifies artifacts centered on one bounded unit of work.
+- The body should make the requested work legible without requiring special tooling.
+- A task artifact should let a later reader tell what work is in scope now and what counts as done.
+- Prose outside `Schema Validation Contract` may explain the schema, but it does not add required validation rules.
+
+### Task Body
+
+Required Shape
+
+- first body heading after the continuity envelope
+- readable prose or lists that state the concrete work, completion signal, and boundaries
+
+Optional Sections
+
+- Subtasks
+- Risks
+- Open Questions
+- Requested Work
+- Acceptance Criteria
+- Blockers
+
+Rules
+
+- A task artifact should begin with a human-readable title.
+- A task artifact should contain enough body content that a later reader can identify the work being requested now.
+- The body should make the current boundaries or constraints readable rather than hiding them in terse metadata.
+- Follow-up sections must not replace the concrete work statement or completion signal.
+- If the artifact becomes mostly design exploration instead of bounded work, another schema should own it instead.
+
+### Task Semantics
+
+Allowed Shapes
+
+- standalone task
+- task with dependencies
+- task with recursive subtasks
+- blocked task with explicit dependency signal
+- task with concrete origin targets
+
+Rules
+
+- A task artifact should make the requested work explicit.
+- A task artifact should make clear what completion means for the current task.
+- A task artifact should make clear what constraints, non-goals, or boundaries still apply.
+- When the task depends on concrete files, traces, or other durable artifacts, the artifact should prefer explicit readable target references over vague mentions.
+- Recursive subtasks are allowed when they clarify execution, but the current task should remain the primary reading unit.
+
+### Task Envelope Companions
+
+Optional Fields
+
+- `Current -> Why`
+- `Current -> Summary`
+- `Current -> Authors`
+- `Current -> Origin`
+
+Rules
+
+- Task artifacts may carry light current-side metadata when it helps a reader orient quickly.
+- Task artifacts should declare parent signal when they continue, refine, or decompose an earlier local artifact.
+- Task artifacts should avoid turning envelope metadata into the only place where the requested work is described.
+
+### File Naming
+
+Allowed Shapes
+
+- `<lineage>.trace.md`
+- `<lineage>-<task-slug>.trace.md`
+
+Rules
+
+- Task artifacts should keep the lineage label first.
+- The optional slug should describe the concrete work slice.
+- Task artifacts should prefer short human-readable slugs.
+- Task artifacts should keep the `.trace.md` suffix stable.
+
+### Interpretation Boundaries
+
+Rules
+
+- Use `tiinex.task.v1` when the artifact is mainly defining concrete work and completion criteria.
+- Do not use `tiinex.task.v1` for broad design exploration without a bounded work request.
+- Do not use `tiinex.task.v1` for thin pointers or passive evidence capture.
+- If the artifact's main job is to land what now governs rather than what should be done, another schema should own it.
+
+## Minimal Example
+
+```md
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.task.v1
+  - Created At: 2026-06-05 00:00:00
+  - Summary: Repair stale schema-note parent links.
+
+---
+
+# Repair Schema Parent Links
+
+## Objective
+
+Replace stale schema-note parent links with the intended committed targets.
+
+## Done Criteria
+
+- parent links point at the intended committed root-schema permalink
+- continuity footer values are refreshed after the rewrite
+
+## Scope
+
+- update only the affected schema-note lineage slice
+
+## Dependencies
+
+- root schema permalink remains readable during the 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 task artifact should stay concrete enough that a reader can tell what work is being requested now
+- recursive subtasks are allowed, but the current task should remain the primary reading unit
+- if the artifact becomes mostly design rationale instead of bounded work, a topic schema may be a better fit
+- if the artifact becomes mainly about what now governs, a decision schema may be a better fit
+
+## Artifact Creation Contract
+
+### Prompt Fields
+
+Required Fields
+
+- version
+- createTitle
+- summaryPrompt
+- summaryPlaceholder
+
+Optional Fields
+
+- whyPrompt
+- whyPlaceholder
+
+Rules
+
+- The current task create surface uses version `1`.
+- `createTitle` should label the create action as `Create Task`.
+- `summaryPrompt` should ask for the task title.
+- `summaryPlaceholder` should guide the user toward the concrete work to be done.
+- `whyPrompt` and `whyPlaceholder` may be omitted when create flow does not ask for a why field.
+
+### Template Body
+
+Required Shape
+
+- first heading uses `# {{summary}}`
+- `## Objective` section
+- `## Done Criteria` section
+- `## Scope` section
+- `## Dependencies` section
+
+Rules
+
+- Generated task artifacts should begin with the task title as the first body heading.
+- `Objective` should describe the concrete work being asked for.
+- `Done Criteria` should define what completion means for the task.
+- `Scope` should capture boundaries, constraints, and non-goals.
+- `Dependencies` should capture blockers, required artifacts, or prerequisite work when they exist.
+- 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/00adbcc5b0319410cf16752a54dcbf4813173040/.topics/.schemas/tiinex.root.v1.schema.md)
+  - Value: BFWYft1v0Ue0gUoO236DGScvnixS7_MIEwO6mhJhkNw
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: SVkacZ6IRAHU68znToXLqDvAKAVRMUqdZHJNAVmmcBc

package/src/schemas/core/topic/.transitions/create-topic-transition-definition.trace.md

@@ -0,0 +1,93 @@
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.transition.definition.v1
+  - Created At: 2026-08-19 00:00:00
+  - Summary: Canonical browser-local standalone Topic creation transition.
+
+---
+
+# Create standalone Topic
+
+## Transition Identity
+
+- Name: Create standalone Topic
+- Version: 1
+- Canonical Identifier: tiinex.site.create-topic.v1
+- Human Label: Topic
+
+## Purpose And Scope
+
+- Purpose: Create one browser-local standalone Topic in the selected workspace.
+- Semantic Boundary: Standalone local Topic creation only; no Parent, relation materialization, remote write, or source provenance is implied.
+
+## Input Roles
+
+- none
+
+## Output Roles
+
+- topic
+  - Meaning: Standalone Topic created by the invocation.
+  - Minimum Count: 1
+  - Maximum Count: 1
+  - Target Kind: artifact
+  - Schema Constraint: tiinex.topic.v1
+  - Generation Binding: target-schema
+
+## Lifecycle And Continuity Effects
+
+### Lifecycle Effects
+
+- create-topic
+  - Target Binding: topic
+  - Effect: create-new
+  - Logical Continuity: new-subject
+  - Required Materialization Operation: create
+
+### Parent Effects
+
+- none
+
+## Relation Effects
+
+- none
+
+## Applicability And Conditions
+
+- Applicability Meaning: A workspace may create one standalone browser-local Topic when exact Topic generation and local placement authority are qualified.
+- Failure Meaning: Topic creation remains unavailable when exact schema, generation, or local placement authority cannot be resolved.
+- Unknown Meaning: Unknown or unavailable authority remains unresolved and must not be guessed.
+
+## Authoring Bindings
+
+- none
+
+## Placement Intent
+
+### Destination Bindings
+
+- workspace-draft
+  - Meaning: Browser-local workspace selected by this invocation.
+  - Required: yes
+
+### Output Placements
+
+- topic-placement
+  - Output Binding: topic
+  - Destination Binding: workspace-draft
+  - Placement Intent: new-materialization
+  - Naming Authority: explicit-binding
+  - Explicit Override Allowed: no
+
+## Interpretation Limits
+
+- Does Not Prove: remote publication, source provenance, Parent ancestry, or relation semantics.
+- Must Not Be Inferred: a source repository, a Parent, a cross-workspace relation, or universal standalone creation for other schemas.
+
+# Continuity Integrity
+
+- bundled-source-identity-v1
+  - Towards: self
+  - Value: tiinex.site.bundle:create-topic-transition-definition.trace.md:v1

package/src/schemas/core/topic/tiinex.topic.v1-transitions.trace.md

@@ -0,0 +1,33 @@
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.schema.transition.companion.v1
+  - Created At: 2026-08-17 00:00:00
+  - Summary: Explicit Topic schema Transition attachment projection.
+
+---
+
+# Topic Schema Transition Companion
+
+## Schema Binding
+
+- Schema Reference: [tiinex.topic.v1](tiinex.topic.v1.schema.md)
+
+## Transition Attachments
+
+- topic-to-task
+  - Transition Reference: [Topic to Task](site-local:src/schemas/core/task/.transitions/topic-to-task-transition-definition.trace.md)
+
+## Interpretation Limits
+
+- Does Not Mean: participation by itself
+- Must Not Be Used To Claim: applicability or execution
+
+---
+
+# Continuity Integrity
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: Uzy3Cqg3qL_0HA67Rq8fg4J7aV1qHhQPunrwOZAXNrY

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

@@ -0,0 +1,197 @@
+# 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/00adbcc5b0319410cf16752a54dcbf4813173040/.topics/.schemas/tiinex.root.v1.schema.md)
+- Current
+  - Current Schema: [tiinex.topic.v1](tiinex.topic.v1.schema.md)
+  - Created At: 2026-05-28 18:11:47
+  - Summary: Schema for bounded topic-oriented lineage artifacts.
+
+---
+
+# Topic
+
+- Status: maintained schema note
+
+## Summary
+
+This schema defines artifacts whose main job is to carry one bounded working
+topic forward.
+
+It is for live design and implementation threads where the reader should be
+able to tell what question, direction, or work slice is currently in motion.
+
+## Schema Validation Contract
+
+### Topic Scope
+
+Applies To
+
+- artifacts whose `Current -> Current Schema` is `tiinex.topic.v1`
+
+Rules
+
+- `tiinex.topic.v1` identifies artifacts centered on one active topic thread.
+- The body should make the current topic legible without requiring special tooling.
+- The topic should stay bounded enough that a reader can tell what is being advanced.
+- Prose outside `Schema Validation Contract` may explain the schema, but it does not add required validation rules.
+
+### Topic Body
+
+Required Shape
+
+- first body heading after the continuity envelope
+- readable prose that advances one bounded topic thread
+
+Optional Sections
+
+- Current Read
+- Design Direction
+- Risks
+- Open Questions
+- Next Artifacts
+- Next Steps
+
+Rules
+
+- A topic artifact should begin with a human-readable title.
+- A topic artifact should contain enough prose to explain the present topic state.
+- Section names inside topic artifacts may vary when the artifact still reads as one coherent thread.
+- Forward-looking sections must not replace the continuity envelope's parent relation.
+
+### Topic Envelope Companions
+
+Optional Fields
+
+- `Current -> Why`
+- `Current -> Summary`
+- `Current -> Authors`
+
+Rules
+
+- Topic artifacts may carry light current-side metadata when it helps a reader orient quickly.
+- Topic artifacts should declare parent signal when they continue an earlier topic artifact.
+- Topic artifacts should avoid turning envelope metadata into the main body content.
+
+### File Naming
+
+Allowed Shapes
+
+- `<lineage>.trace.md`
+- `<lineage>-<topic-slug>.trace.md`
+
+Rules
+
+- Topic artifacts should keep the lineage label first.
+- The optional slug should describe the active topic thread.
+- Topic artifacts should prefer short human-readable slugs.
+- Topic artifacts should keep the `.trace.md` suffix stable.
+
+### Interpretation Boundaries
+
+Rules
+
+- Use `tiinex.topic.v1` when the artifact is mainly preserving or advancing a working topic.
+- Do not use `tiinex.topic.v1` for schema notes, opaque dumps, or generic holding files.
+- If the artifact's main job is to make a decision rather than hold a topic thread, another schema should own it.
+
+## Minimal Example
+
+```md
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.topic.v1
+  - Created At: 2026-06-04 00:00:00
+  - Summary: Topic root for the validation tightening pass.
+
+---
+
+# Validation Tightening
+
+This topic captures the current direction for the work.
+
+## Current Read
+
+The schema validator now owns both machine contract shape and maintained body structure.
+```
+
+## 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
+
+- topic artifacts should remain readable to humans without special tooling
+- the envelope still carries continuity and integrity metadata
+- free markdown inside owned sections is fine when the thread remains legible
+- the validator should own the maintained schema shape rather than relying on convention alone
+
+## Artifact Creation Contract
+
+### Prompt Fields
+
+Required Fields
+
+- version
+- createTitle
+- summaryPrompt
+- summaryPlaceholder
+
+Optional Fields
+
+- whyPrompt
+- whyPlaceholder
+
+Rules
+
+- The current topic create surface uses version `1`.
+- `createTitle` should label the create action as `Create Topic`.
+- `summaryPrompt` should ask for the topic title.
+- `summaryPlaceholder` should guide the user toward the active topic.
+- `whyPrompt` and `whyPlaceholder` may be omitted when create flow does not ask for a why field.
+
+### Template Body
+
+Required Shape
+
+- first heading uses `# {{summary}}`
+- summary sentence placeholder below the title
+- `## Current Read` section
+- `## Design Direction` section
+- `## Next Artifacts` section
+
+Rules
+
+- Generated topic artifacts should begin with the topic title as the first body heading.
+- The generated body should include one orienting sentence before the first named section.
+- `Current Read` should explain the present topic state.
+- `Design Direction` should state where the topic should move next.
+- `Next Artifacts` should leave room for concrete follow-up artifacts.
+- 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/00adbcc5b0319410cf16752a54dcbf4813173040/.topics/.schemas/tiinex.root.v1.schema.md)
+  - Value: BFWYft1v0Ue0gUoO236DGScvnixS7_MIEwO6mhJhkNw
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: NXenBNGbXjmQid1IzVP7DbcNt0iweaEz8k9yq0aVXII

package/src/schemas/core/topic/topic-semantic-package.trace.md

@@ -0,0 +1,53 @@
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.semantic.package.v1
+  - Created At: 2026-08-17 00:00:00
+  - Summary: Topic semantic package for schema-local Transition discovery.
+
+---
+
+# Topic Semantic Package
+
+## Package Identity
+
+- Package Name: Topic
+- Purpose: Site-local semantic neighborhood for the canonical Topic schema and reverse Transition discoverability.
+
+## Package Boundary
+
+- Boundary Root: manifest-directory
+- Discovery Policy: recursive-within-boundary
+- Nested Package Policy: explicit-only
+
+## Included Packages
+
+- none
+
+## External Package Dependencies
+
+- Task Package
+  - Package Reference: [Task Package](site-local:src/schemas/core/task/task-semantic-package.trace.md)
+
+## Schema Resolution Bindings
+
+- tiinex.topic.v1
+  - Schema Reference: [tiinex.topic.v1](tiinex.topic.v1.schema.md)
+
+- tiinex.task.v1
+  - Schema Reference: [tiinex.task.v1](site-local:src/schemas/core/task/tiinex.task.v1.schema.md)
+  - Package Reference: [Task Package](site-local:src/schemas/core/task/task-semantic-package.trace.md)
+
+## Interpretation Limits
+
+- Does Not Mean: package ownership of Transition semantic truth
+- Must Not Be Used To Claim: participation, applicability, executability, authorization, ordering, recommendation, or UI visibility
+
+---
+
+# Continuity Integrity
+
+- sha256-base64url-c14n-v2
+  - Towards: self
+  - Value: gXgsvbRou5C_d9t8TBXnzApiseG_pTNeXbk3rYqGY4o