@tiinex/app 0.1.1

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

@@ -0,0 +1,239 @@
+# 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.signal.v1](tiinex.signal.v1.schema.md)
+  - Created At: 2026-06-14 00:00:00
+  - Summary: Schema for bounded signal artifacts that preserve observed indicators without overclaiming evidence.
+
+---
+
+# Signal
+
+- Status: maintained schema note
+
+## Summary
+
+This schema defines artifacts whose main job is to preserve a bounded signal:
+an observed reaction, weak indicator, external response, status cue, or other
+interpretable sign that bears on a lineage without necessarily becoming
+evidence, feedback, task, or decision.
+
+It is for lightweight observations that matter enough to keep traceable, but
+should not be overstated as proof.
+
+## Schema Validation Contract
+
+### Signal Scope
+
+Applies To
+
+- artifacts whose `Current -> Current Schema` is `tiinex.signal.v1`
+
+Rules
+
+- `tiinex.signal.v1` identifies artifacts centered on one bounded observed signal.
+- A signal artifact should state what was observed and what it may indicate.
+- A signal artifact should not overclaim certainty beyond the observed signal.
+- A signal artifact may preserve positive, negative, neutral, ambiguous, or absent signal.
+- Prose outside `Schema Validation Contract` may explain the schema, but it does not add required validation rules.
+
+### Signal Body
+
+Required Shape
+
+- first body heading after the continuity envelope
+- `## Observed Signal` section
+- `## Source` section
+- `## Interpretation` section
+- `## Limits` section
+
+Optional Sections
+
+- Signal Strength
+- Linked Artifacts
+- Evidence Material
+- Follow-Up
+- Next Artifacts
+
+Rules
+
+- A signal artifact should begin with a human-readable title.
+- `Observed Signal` should describe the signal itself.
+- `Source` should name where the signal came from when known.
+- `Interpretation` should state what the signal may bear on without turning it into stronger evidence than it is.
+- `Limits` should state ambiguity, uncertainty, missing context, or reasons not to overread the signal.
+- A signal artifact should contain enough body content that a later reader can identify the signal and its relevance.
+- When the signal is based on a screenshot, comment, notification, metric, or external artifact, the body should include a readable reference or description.
+- If the artifact mainly preserves supporting material for a specific claim, an evidence schema should own it instead.
+- If the artifact contains directed response that should be dispositioned or acted on, a feedback schema should own it instead.
+
+### Signal Semantics
+
+Allowed Shapes
+
+- social reaction
+- external response
+- status cue
+- weak adoption signal
+- absence-of-response signal
+- ambiguous observation
+- metric or count snapshot with limits
+
+Rules
+
+- A signal artifact should make clear whether the signal is direct, indirect, weak, ambiguous, or negative.
+- A signal artifact should not hide that a signal is based on partial observation.
+- A signal artifact may support later topic, feedback, decision, task, or evidence artifacts, but does not replace them.
+- When a signal is time-sensitive or platform-dependent, the artifact should say so.
+- When the signal could be explained by multiple causes, the artifact should preserve that ambiguity.
+
+### Signal Envelope Companions
+
+Optional Fields
+
+- `Current -> Why`
+- `Current -> Summary`
+- `Current -> Authors`
+- `Current -> Origin`
+- parent signal when the signal continues or refines an earlier local artifact
+
+Rules
+
+- Signal artifacts may carry light current-side metadata when it helps a reader orient quickly.
+- Parent signal should be used when a signal artifact continues a local signal thread.
+- Envelope metadata should support, not replace, body-level observation and limits.
+
+### File Naming
+
+Allowed Shapes
+
+- `<lineage>.trace.md`
+- `<lineage>-<signal-slug>.trace.md`
+
+Rules
+
+- Signal artifacts should keep the lineage label first.
+- The optional slug should describe the observed signal or source.
+- Signal artifacts should prefer short human-readable slugs.
+- Signal artifacts should keep the `.trace.md` suffix stable.
+
+### Interpretation Boundaries
+
+Rules
+
+- Use `tiinex.signal.v1` when the artifact is mainly preserving a bounded signal with interpretation limits.
+- Do not use `tiinex.signal.v1` for landed decisions, bounded tasks, broad topics, or raw runtime exports.
+- Do not use `tiinex.signal.v1` for directed feedback that needs disposition.
+- Do not use `tiinex.signal.v1` to make weak observations look like strong evidence.
+
+## Minimal Example
+
+```md
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.signal.v1
+  - Created At: 2026-06-14 00:00:00
+  - Summary: Weak external signal from a GitHub discussion reaction.
+
+---
+
+# GitHub Reaction Signal
+
+## Observed Signal
+
+- A public comment received one positive reaction.
+
+## Source
+
+- Source: GitHub discussion UI observation
+
+## Interpretation
+
+- The reaction may indicate that the comment was noticed or found useful by at least one reader.
+
+## Limits
+
+- The reaction does not prove project acceptance, maintainer interest, or correctness.
+```
+
+## 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
+
+- signal is intentionally weaker than evidence and feedback
+- signal preserves observations without forcing premature action or certainty
+- signal artifacts should help later readers understand why something was noticed without overclaiming what it proves
+
+## Artifact Creation Contract
+
+### Prompt Fields
+
+Required Fields
+
+- version
+- createTitle
+- summaryPrompt
+- summaryPlaceholder
+
+Optional Fields
+
+- whyPrompt
+- whyPlaceholder
+
+Rules
+
+- The current signal create surface uses version `1`.
+- `createTitle` should label the create action as `Create Signal`.
+- `summaryPrompt` should ask for the signal title.
+- `summaryPlaceholder` should guide the user toward the observed signal.
+- `whyPrompt` and `whyPlaceholder` may be omitted when create flow does not ask for a why field.
+
+### Template Body
+
+Required Shape
+
+- first heading uses `# {{summary}}`
+- `## Observed Signal` section
+- `## Source` section
+- `## Interpretation` section
+- `## Limits` section
+
+Rules
+
+- Generated signal artifacts should begin with the signal title as the first body heading.
+- `Observed Signal` should state what was observed.
+- `Source` should state where the signal came from.
+- `Interpretation` should state what the signal may bear on.
+- `Limits` should prevent overclaiming the signal.
+- 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: IiDpQlRGL1WC5jCykMwSjdzXXHy70_-7z95ATooBfWE

package/src/schemas/core/task/.transitions/create-task-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 Task creation transition.
+
+---
+
+# Create standalone Task
+
+## Transition Identity
+
+- Name: Create standalone Task
+- Version: 1
+- Canonical Identifier: tiinex.site.create-task.v1
+- Human Label: Task
+
+## Purpose And Scope
+
+- Purpose: Create one browser-local standalone Task in the selected workspace.
+- Semantic Boundary: Standalone local Task creation only; no Parent, relation materialization, remote write, or source provenance is implied.
+
+## Input Roles
+
+- none
+
+## Output Roles
+
+- task
+  - Meaning: Standalone Task created by the invocation.
+  - Minimum Count: 1
+  - Maximum Count: 1
+  - Target Kind: artifact
+  - Schema Constraint: tiinex.task.v1
+  - Generation Binding: target-schema
+
+## Lifecycle And Continuity Effects
+
+### Lifecycle Effects
+
+- create-task
+  - Target Binding: task
+  - 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 Task when exact Task generation and local placement authority are qualified.
+- Failure Meaning: Task 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
+
+- task-placement
+  - Output Binding: task
+  - 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-task-transition-definition.trace.md:v1

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

@@ -0,0 +1,102 @@
+# Continuity Context
+
+- Envelope Schema: tiinex.root.v1
+- Current
+  - Current Schema: tiinex.transition.definition.v1
+  - Created At: 2026-08-17 00:00:00
+  - Summary: Canonical browser-local Topic to Task product transition.
+
+---
+
+# Topic to Task
+
+## Transition Identity
+
+- Name: Topic to Task
+- Version: 1
+- Canonical Identifier: tiinex.site.topic-to-task.v1
+- Human Label: Create task
+
+## Purpose And Scope
+
+- Purpose: Create one browser-local Task that directly continues the selected Topic.
+- Semantic Boundary: Canonical local Task creation only; no remote write, repository path allocation, relation materialization, or source mutation.
+
+## Input Roles
+
+- source-topic
+  - Meaning: Topic used as the direct continuity source.
+  - Minimum Count: 1
+  - Maximum Count: 1
+  - Target Kind: artifact
+  - Schema Constraint: tiinex.topic.v1
+  - Acquisition Policy: existing-only
+
+## Output Roles
+
+- task
+  - Meaning: Task created by the invocation.
+  - Minimum Count: 1
+  - Maximum Count: 1
+  - Target Kind: artifact
+  - Schema Constraint: tiinex.task.v1
+  - Generation Binding: target-schema
+
+## Lifecycle And Continuity Effects
+
+### Lifecycle Effects
+
+- create-task
+  - Target Binding: task
+  - Effect: create-new
+  - Logical Continuity: new-subject
+  - Required Materialization Operation: create
+
+### Parent Effects
+
+- task-continues-topic
+  - Output Binding: task
+  - Parent Binding: source-topic
+  - Effect: set
+
+## Relation Effects
+
+- none
+
+## Applicability And Conditions
+
+- Applicability Meaning: A currently selected canonical Topic may create one local Task when the invocation and materialization plan qualify.
+- Failure Meaning: Creation remains unavailable when canonical authority, bindings, Parent recovery, or materialization preflight cannot be qualified.
+- 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
+
+- task-placement
+  - Output Binding: task
+  - Destination Binding: workspace-draft
+  - Placement Intent: new-materialization
+  - Naming Authority: explicit-binding
+  - Explicit Override Allowed: no
+
+## Interpretation Limits
+
+- Does Not Prove: remote publication, repository path allocation, generic relation execution, Condition evaluation, or filesystem materialization.
+- Must Not Be Inferred: a repository path, File Naming resolver, source mutation, or legacy continuation semantics.
+
+# Continuity Integrity
+
+- bundled-source-identity-v1
+  - Towards: self
+  - Value: tiinex.site.bundle:topic-to-task-transition-definition.trace.md:v1

package/src/schemas/core/task/task-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: Task semantic package for schema-local Transition discovery.
+
+---
+
+# Task Semantic Package
+
+## Package Identity
+
+- Package Name: Task
+- Purpose: Site-local semantic neighborhood for the canonical Task schema and Task-oriented Transition discovery.
+
+## Package Boundary
+
+- Boundary Root: manifest-directory
+- Discovery Policy: recursive-within-boundary
+- Nested Package Policy: explicit-only
+
+## Included Packages
+
+- none
+
+## External Package Dependencies
+
+- Topic Package
+  - Package Reference: [Topic Package](site-local:src/schemas/core/topic/topic-semantic-package.trace.md)
+
+## Schema Resolution Bindings
+
+- tiinex.task.v1
+  - Schema Reference: [tiinex.task.v1](tiinex.task.v1.schema.md)
+
+- tiinex.topic.v1
+  - Schema Reference: [tiinex.topic.v1](site-local:src/schemas/core/topic/tiinex.topic.v1.schema.md)
+  - Package Reference: [Topic Package](site-local:src/schemas/core/topic/topic-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: Ba4sghoxq8OjlFLJvc168getEQESikdcvctB4FLP0vo

package/src/schemas/core/task/tiinex.task.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 Task schema Transition attachment projection.
+
+---
+
+# Task Schema Transition Companion
+
+## Schema Binding
+
+- Schema Reference: [tiinex.task.v1](tiinex.task.v1.schema.md)
+
+## Transition Attachments
+
+- topic-to-task
+  - Transition Reference: [Topic to 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: NG86jbaIvc2hB9bcyPC_BlSHmqdBkf_jUYDnlrSZTkI

package/src/schemas/core/task/tiinex.task.v1.authoring.js

@@ -0,0 +1,65 @@
+import { TASK_CANONICAL_REQUIRED_INPUTS } from '@tiinex/core/schemas/core/task/tiinex.task.v1.contract.js';
+
+export function readCanonicalTaskAuthoringValues(markdown = '') {
+  const text = normalize(markdown);
+  const sections = rawArtifactSections(text);
+  const summary = currentSummary(sections.envelope);
+  const values = { Summary: summary };
+  for (const name of TASK_CANONICAL_REQUIRED_INPUTS.slice(1)) values[name] = sectionBody(sections.body, name);
+  const qualified = TASK_CANONICAL_REQUIRED_INPUTS.every((name) => values[name] !== undefined && String(values[name]).trim() !== '');
+  return Object.freeze({ qualified, values: Object.freeze(values), requiredInputs: TASK_CANONICAL_REQUIRED_INPUTS });
+}
+
+export function renderCanonicalTaskEditMarkdown(originalMarkdown = '', inputValues = {}) {
+  const parsed = readCanonicalTaskAuthoringValues(originalMarkdown);
+  if (!parsed.qualified) return Object.freeze({ state: 'unqualified', reason: 'canonical-task-authoring-shape-unavailable', markdown: '' });
+  const values = Object.fromEntries(TASK_CANONICAL_REQUIRED_INPUTS.map((name) => [name, String(inputValues[name] ?? '')]));
+  if (TASK_CANONICAL_REQUIRED_INPUTS.some((name) => !values[name].trim())) return Object.freeze({ state: 'unqualified', reason: 'canonical-task-authoring-input-missing', markdown: '' });
+  const raw = rawArtifactSections(normalize(originalMarkdown));
+  const envelope = replaceCurrentSummary(raw.envelope, values.Summary);
+  const body = `# ${values.Summary}\n\n${TASK_CANONICAL_REQUIRED_INPUTS.slice(1).map((name) => `## ${name}\n\n${values[name]}`).join('\n\n')}`;
+  const integrity = raw.integrity ? `\n\n${raw.integrity}` : '';
+  return Object.freeze({ state: 'rendered', markdown: `${envelope}\n\n---\n\n${body}${integrity}\n`, values: Object.freeze(values) });
+}
+
+function rawArtifactSections(markdown = '') {
+  const text = normalize(markdown).trim();
+  const boundary = /^---\s*$/m.exec(text);
+  if (!boundary) return { envelope: text, body: '', integrity: '' };
+  const envelope = text.slice(0, boundary.index).trimEnd();
+  const remainder = text.slice(boundary.index + boundary[0].length).replace(/^\n/, '');
+  const integrityIndex = remainder.search(/^# Continuity Integrity\s*$/m);
+  return {
+    envelope,
+    body: (integrityIndex === -1 ? remainder : remainder.slice(0, integrityIndex)).trim(),
+    integrity: integrityIndex === -1 ? '' : remainder.slice(integrityIndex).trim()
+  };
+}
+function currentSummary(envelope = '') {
+  const lines = normalize(envelope).split('\n');
+  const start = lines.findIndex((line) => /^-\s+Current\s*$/.test(line));
+  if (start === -1) return '';
+  for (let i = start + 1; i < lines.length; i += 1) {
+    if (/^-\s+\S/.test(lines[i])) break;
+    const match = lines[i].match(/^\s+-\s*Summary:\s*(.*)$/);
+    if (match) return match[1].trim();
+  }
+  return '';
+}
+function replaceCurrentSummary(envelope = '', summary = '') {
+  const lines = normalize(envelope).split('\n');
+  const start = lines.findIndex((line) => /^-\s+Current\s*$/.test(line));
+  if (start === -1) return envelope;
+  for (let i = start + 1; i < lines.length; i += 1) {
+    if (/^-\s+\S/.test(lines[i])) break;
+    const match = lines[i].match(/^(\s+)-\s*Summary:\s*(.*)$/);
+    if (match) { lines[i] = `${match[1]}- Summary: ${summary}`; break; }
+  }
+  return lines.join('\n');
+}
+function sectionBody(body = '', name = '') {
+  const escaped = String(name).replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+  const match = normalize(body).match(new RegExp(`^## ${escaped}\\n\\n([\\s\\S]*?)(?=\\n\\n## |$)`, 'm'));
+  return match ? match[1].trimEnd() : undefined;
+}
+function normalize(value = '') { return String(value || '').replace(/\r\n?/g, '\n'); }