Chronal Studio documentation

Core concepts

The few ideas Chronal tracks: people and things, events, changing facts, knowledge, time, and sources.

Chronal connects ordinary writing to a small set of facts and events that it can follow over time. You do not need to structure every sentence. Track only the information you need to ask about, compare, check, or trace back to a source.

People, places, things, and events

Chronal calls a person, place, organization, object, or other lasting subject an object. The name is broad because the same rules can cover a character, a city, a document, or a piece of equipment.

An event is something meaningful that happens. Giving an event a date lets Chronal connect a change to a point or span in time.

Changing facts and knowledge

A property is a fact about something, such as a person’s role, a ship’s location, or who owns an item. Properties can change through events.

Knowledge records what a person or character knows or believes. It stays separate from what the project treats as true. That distinction lets someone act on incomplete information without changing the project’s overall record.

Time and point-in-time views

A date can be as precise as your project requires. A snapshot, or point-in-time view, answers: what was true at this moment? Chronal Engine calculates which facts, knowledge records, and relationships applied then.

Cause and effect

You can record that one event caused another or changed a fact. Chronal keeps those specific claims separate from ordinary links between related records.

Source history

A source trace answers: where did this answer come from, when did it apply, and which earlier information did it replace? The technical name for that history is provenance.

Keeping the source with the answer is a core trust feature. It lets you inspect Chronal’s reasoning instead of accepting a conclusion without context.