Chandra Core

Chain Statistics
connecting
chandraprotocol.com
Context Units
Total number of Context Units ever published to this Chandra instance across all spokes. Every successful call to /api/cu/publish increments this count. The number only grows — CUs are immutable and cannot be deleted.
total commits
Spokes
Total number of spokes — governed subjects with at least one CU. A spoke is created automatically on first publish to a new subject_id, or explicitly via /api/spoke/create. Each spoke is an independent hash chain.
active subjects
Days Active
Number of distinct calendar days (UTC) on which at least one CU was published. Derived from the last 365 days shown in the heatmap. A day with zero commits does not count — only days where the chain actually grew.
days with commits
Last Commit
Timestamp of the most recently published CU across all spokes. Shown as relative time — e.g. "4m ago". Timestamps are stored as Common Lisp universal-time (seconds since 1900-01-01 UTC) and converted to local display time in the browser.
Commit Activity
Each cell represents one calendar day. Color intensity reflects commit volume — the number of Context Units published that day. Hover any cell for the exact date and count. A commit is any successful call to /api/cu/publish. The chart spans the last 365 days.
loading chain data…
Subject Types
CUs are categorized by subject_type at publish time. This shows the distribution of artifact categories across the chain — e.g. protocol-specification, agent-log, decision-record. Useful for understanding what kinds of work the chain is recording.
By Author
Attribution is required by the Chandra protocol — every CU records who acted. Human commits show the human_author value set at publish time. CUs with no human author are attributed to "agent" — machine-produced artifacts where no human was named.
Most Active Subjects
A spoke is a governed subject — a distinct chain of CUs sharing the same subject_id. Ranked by total commit count, highest first. Top 10 shown. Use the test client to drill into any spoke's full lineage and verify its chain integrity.
Recent Activity last 10 commits
The 10 most recently published CUs across all spokes, newest first. Dot color indicates commit type: green = human-authorized commit, grey = agent commit (no human_author), purple = merge CU (two branches reconciled). Merge operations require human authorization per GR-PROV-016.
Page Traffic
Daily page hit counts tracked client-side and flushed to the server log. UTC dates throughout. Auto-saved every 5 minutes and on page close. Use Save Log to flush immediately. Data survives server reboots via the traffic.log file reloaded on startup. Week selector steps through all recorded weeks.
loading traffic data…