Stax Digital Garden

TRC-1008 - Project Manifest Binding and Horizon Aggregation

2 min read

Living Document Notice
Published 2026-09-17. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

Project Manifest Binding and Horizon Aggregation

Project Manifest Binding and Horizon Aggregation: Dual-trace Phosphor P20 safety amber and P22R ruby red vector CRT macro showing central parent project manifest node aggregating radiating child task vectors

Summary

Atomic tasks must coalesce into coherent multi-week projects without rigid relational databases. Trice utilizes YAML project manifests and parent-child graph bindings to aggregate completion percentages, critical paths, and milestone deadlines.

Bridging the Gap Between Tasks and Projects

GTD defines a ‘Project’ as any outcome requiring more than one action step. In file-based knowledge management, projects often dissolve into loose folders of random notes or gigantic monolithic documents where individual tasks cannot be tracked by automated scripts.

Trice formalizes projects through structured Project Manifests. A manifest is an authoritative parent node that aggregates multiple child tasks across directory boundaries.

+-------------------------------------------------------------+
|                Trice Project Manifest Topology              |
|                                                             |
|   +-----------------------------------------------------+   |
|   | Project Manifest: PRJ-0100                          |   |
|   | "Columnar WAL Engine v1.0 Release"                  |   |
|   +-----------------------------------------------------+   |
|            │                     │                     │    |
|       [childTask]           [childTask]           [childTask]|
|            v                     v                     v    |
|   +-----------------+   +-----------------+   +------------+|
|   | TRC-1001: WAL   |   | TRC-1002: BTree |   | TRC-1004:  ||
|   | State: Done     |   | State: Active   |   | State: Wait||
|   +-----------------+   +-----------------+   +------------+|
+-------------------------------------------------------------+

Project Manifest Schema

Project manifests reside in 03-trice/projects/ and declare target milestones, outcome definitions, and child task arrays:

---
title: "PRJ-0100: Columnar WAL Engine Release"
project_status: active
target_milestone: "2026-10-15"
$pkm:
  id: "urn:uuid:0191fa30-3001-7000-8000-000000000100"
  realm: trice
  type: project_manifest
  relations:
    containsTask:
      - "urn:trice:task:0191fa30-3001-7000-8000-000000000001"
      - "urn:trice:task:0191fa30-3001-7000-8000-000000000002"
      - "urn:trice:task:0191fa30-3001-7000-8000-000000000004"
---
 
# Columnar WAL Engine Release
 
## Desired Outcome
The local SQLite storage engine persists 100,000 transactions per second with zero-copy WAL page buffers.

Automated Progress Rollup

When queried, the Trice engine traverses containsTask relations and computes project health metrics on the fly:

SELECT 
    prj.title,
    COUNT(task.id) AS total_tasks,
    SUM(CASE WHEN task.task_state = 'completed' THEN 1 ELSE 0 END) AS completed_tasks,
    ROUND(AVG(CASE WHEN task.task_state = 'completed' THEN 1.0 ELSE 0.0 END) * 100, 1) AS progress_pct
FROM projects prj
JOIN relations rel ON rel.source_id = prj.id
JOIN tasks task ON task.id = rel.target_urn
WHERE prj.id = 'urn:trice:project:0191fa30-3001-7000-8000-000000000100'
GROUP BY prj.id;

This dynamic computation eliminates manual status reporting while ensuring that child tasks remain autonomous, movable, and individually verifiable.

  • Directus Target: trice
  • Garden Source Reference: MOC - Bosun PKM Tools, MOC - Fleet Operations
  • Garden Source Reference: [TRC-1008 - Project Manifest Binding and Horizon Aggregation](TRC-1008 - Project Manifest Binding and Horizon Aggregation)

Graph View