Ticket graphs

Every ticket as the root of its provenance graph — goal, patch, approval, runs and (as the ticket-class build lands) mandate, manifestations, guarantees, journey, artifacts and children. Rendered through the <<<TicketGraphList>>> tag.

← all ticket-graphs

CLOSED#47 build

REST interface for every table

goal

Generic REST layer over every table in the unified DB. Read-only first increment SHIPPED: boot/rest.php, dispatched by router.php on ?api= — ?api=tables (discovery), ?api=<table> (paginated JSON), ?api=<table>&id=<pk> (single row); table name allowlisted against sqlite_master. Follow-up: writes (POST/PUT/DELETE) with validation + auth, and a REST view/console. Precedent: the tracker ticket.py REST + human view. [progress] REST CREATE (POST) shipped + tested (column-validated insert). Remaining: UPDATE (PUT) and DELETE by id, plus auth. [done] Full REST CRUD (GET/POST/PUT/DELETE) shipped + tested; pk-protected, column-validated, single-row writes. Auth still a follow-up.

patch

none

approval

unapproved

runs

no runs recorded

mandate (clauses)

not yet recorded — lands with the ticket-class build

manifestations

not yet recorded — lands with the ticket-class build

guarantees

not yet recorded — lands with the ticket-class build

journey (blunders & successes)

not yet recorded — lands with the ticket-class build

artifacts (forge)

not yet recorded — lands with the ticket-class build

source (forge tree)

browse congruency source (forge-parked tree)

children

not yet recorded — lands with the ticket-class build