Production

Slate

Jalaran Slate is a production tracker that computes each episode’s real stage from the records that exist, instead of from a status somebody remembered to update.

Open Slate →Create free account

Who Slate is for

For anyone running a content pipeline who has learned not to trust their own board. If you have ever seen a card marked done next to a deliverable that was never made, Slate is built around removing the possibility rather than asking you to be more careful.

What Slate does

Slate holds episodes with typed links to the Lore, Puppet and Premiere records that belong to them, and derives each episode’s stage on every read — not from whether a linked record exists, but from what that record actually contains. The distinction matters: a publication package is created empty, and a render job can fail. Treating the existence of a row as evidence of finished work is exactly how a board starts lying. There is also a cadence view answering the question the module exists for, which is whether you are actually keeping to your schedule.

Stage derived from real artifacts, never hand-set
Typed links across the script, render and packaging records
Cadence view with three-state health rather than a pass/fail
Markdown export led by the cadence answer

How Slate works

Create an episode
One record per episode, with a target date.
Link the real artifacts
Typed links to the script, the render and the publication package as each one comes into existence.
Read the derived stage
Status is computed on every view from what those records contain. It is never stored and never set by hand.
Check your cadence
A three-state health view across episodes, so slipping is visible while it is still recoverable.

What Slate does not do

Slate tracks the Jalaran content pipeline specifically — it reads Lore, Puppet and Premiere records and nothing else, so it is not a general project tracker and will not model arbitrary work. It has no AI in it at all: this is scheduling and status computation, deliberately. It reports what the artifacts prove and is explicit about what it cannot verify, which means it will sometimes show an episode as less advanced than you feel it is.

Common questions

Why can I not just set an episode’s status myself?

Because a hand-set status is the thing that goes stale. Status is derived on every read from what the linked records actually contain, so the board cannot claim work is done when the artifact is missing or the render failed.

Can I use it to track work outside the content pipeline?

No. It understands the specific record types the pipeline produces. For general personal work, Tasks is the right module.

Does it use AI?

No. Slate is pure scheduling and status computation with no model call anywhere in it, which is also why it keeps working when the local model server is off.