README - SyberLabs/RISE GitHub Wiki

RISE product library and team tracker

The Reader and the ChatGPT Composer (with RiseSDK later) are equal product directions. Shared foundations connect specific tasks; research in one lane does not automatically hold the other. Start the local team dashboard with npm run roadmap:dev, then open the loopback address printed by the command. The dashboard is read-only and refreshes while agents update task files. It is separate from the public reader. Each dashboard reflects the checkout serving it; updates from other branches appear after their commits are integrated. Seth can run the same commands in his checkout. Git review resolves cross-branch updates.

Current direction and truth

Source Role
Task records Current work state, owners, dependencies and linked evidence; validated JSON, one file per task
Reader direction Website scope and near-term acceptance packages; Intent
Consolidated Reader Canonical Home, four reader choices, one catalog and colour vocabulary, the plugin boundary and build order; Intent, decided 2026-10-05
Consolidated Reader decisions The answers to its six questions; Record
One colour vocabulary design B2a: the theme-to-engine map beside RISE_CURRENT_THEMES, seven pull requests, five owner questions; Record
Canonical Home design B4: the still window over the featured reading's field, Begin the one key, eight pull requests, five owner questions; Record
Mystery School complete library The sourcing survey and the School-corpus design that take the school from 4 to 66 readable texts without touching the Archive canon; Proposal, RDR-030
Mystery School plan The owner's graded canon of 66 public domain texts in seven houses, with reading paths; Intent, retained verbatim, built as RDR-029 (design)
Reader evidence Production probes, capabilities and 14 days of history behind the Consolidated Reader; Record
Composer decision Composer is the approach in ChatGPT; Dive and realtime Live out of current scope; Record
Composer-first roadmap Composer delivery sequence M0–M4 (M3 removed); Intent
October decisions Dated conversation summary and provenance; Record
Tracker design Tracker architecture and boundaries; approved Intent implemented by this tool
Experience Program Durable score Contract
System architecture Runtime architecture Contract
Human release acceptance Human evidence Contract

Status and delivery are independent. done means a task's stated scope is complete, not that the product is released. A merged implementation task can coexist with unstarted acceptance tasks. Dashboard readiness depends on completed task dependencies. No percentage is presented as a measure of reader value or release readiness.

Agent update workflow

  1. Read this index and the lane's direction. Run npm run roadmap:check and choose a ready task; inspect dependencies and acceptance before coding.
  2. Claim the task with one owner and an activity summary. Do not replace an active owner without coordination. Keep one narrow PR and respect file ownership.
  3. Update the task in the same PR as the work. Link commits/PRs, exact test evidence and human observations; distinguish branch, merged, deployed and accepted. No tokens or participant data.
  4. Validate the full graph before committing. Never infer task completion from a green build or merged PR alone. Reconcile acceptance and evidence, and record remaining blockers.

CLI example (run from the repository):

node scripts/roadmap.mjs validate
node scripts/roadmap.mjs update LIVE-003 --patch patch.json --expect-revision 1 --summary "Claimed fixture preparation"

patch.json contains only the fields to change, for example:

{"owner":"agent-fixtures","status":"in_progress"}

The CLI adds an activity entry, timestamp and revision after validating the candidate graph. A stale expected revision fails without changing the record. For richer updates, edit one JSON record directly, increment revision, update timestamp/activity and run validation. Git review resolves cross-branch conflicts; the CLI is not a multi-user locking service. Patch files are temporary local inputs, not new task records.

Commands: npm run roadmap:check, npm run test:roadmap, npm run roadmap:dev, npm run roadmap:build. Static output is an explicitly dated snapshot; re-run the build for current state. Shared hosting and dashboard writes are deferred until content/access review. Recent Git history includes unlinked work so the team can classify it instead of silently omitting it.

Product discussions and earlier direction

The collection preserves available source documents and summaries. It is not a complete transcript of every chat or external MasterMind discussion. Historical proposals retain their dates and do not override current contracts.

October engineering context

Published from docs/product/README.md. Edits made here are overwritten on the next push to main.