Record the election
The Council Election event establishes John Baldwin as mayor at a dated point in the project.
Use cases
Understand what changed, when it changed, and why.
Chronal Studio is useful when a project spans many dates, a fact can stop being true, or an answer needs to remain connected to its source.
01 / Included public demo
Continuity checks
“Who was mayor in 1825—and why?”
Greyhaven is a compact public demo. It shows how a dated election changes an earlier record and how you can inspect the source behind the answer.
Choose the year 1825
Chronal Engine works out which mayor record applied then instead of assuming the newest note has always been true.
Open the source trace
Studio shows John Baldwin, the Council Election that supports the answer, and the earlier Unknown record that no longer applies.
Greyhaven DemoAsk what was true
A guided question about Greyhaven in 1825
Greyhaven DemoTrace the answer
The supporting source and the earlier record it replaced
A useful fit forHistorical recordsOperational decisionsLong-running knowledge bases
02 / Fiction workflow
Worldbuilding and long-form fiction
“What changed between 2029 and 2048?”
In Perception Anchor, the timeline keeps people, events, different points of view, and long spans of time coherent across a fictional world.
Perception AnchorRead the authored chronology
Four tracks, dated events, and the selected source record
Check sequence
See dated events and active spans together, including gaps and overlaps that are hard to reconstruct file by file.
Preserve perspective
Keep what a character knows separate from what the story treats as true, so incomplete knowledge does not rewrite the whole world.
Return to prose
Select an event in the chronology, then move directly back to the written record that establishes it.
A useful fit forNovels and seriesShared universesContinuity editing
03 / Research workflow
Research and investigation
“Which records are connected—and which events are said to have caused another?”
In this research example, Chronal separates ordinary connections from specific cause-and-effect claims while keeping each item connected to the record behind it.
Somebody's Gotta Help MeFollow the relationships
A focused event and its connected records
Somebody's Gotta Help MeSeparate cause from connection
Cause-and-effect claims shown apart from ordinary links
Follow people and records
Focus a person, document, or event and inspect the surrounding network without losing the source behind it.
Separate link from cause
Use one map for general connections and another for specific claims about what led to what.
Reconstruct what was knowable
Choose a date to see what the records established then instead of applying a later conclusion to the whole history.
A useful fit forInvestigative reportingCase researchEvidence-led analysis
A simple fit check
Chronal earns its place when change needs evidence.
Important facts in your project change over time.
You need to preserve who knew what, not only what the project treats as true.
You need to explain why a conclusion applies at a chosen time, not simply repeat it.
You want the computer to track these details without hiding your work in a hosted system.
Follow the Greyhaven workflow.
The site uses Greyhaven Demo to show how Chronal records a change, answers what was true, and reveals the source behind the answer. Chronal Studio is coming soon.