Product documentation

How the operating system is structured.

A public guide to the product model, the status of each surface, and the boundaries that keep representation separate from project truth. Cadentis is organized as a connected system: Stratum represents physical infrastructure, Cascade represents project milestones and dependencies, and Anticipate reasons over that state to surface a proposed intervention.

Working principle

The interface may simplify complexity. The underlying evidence and authority must remain visible.

Public infrastructure context.

Stratum presents transmission, substations, generation, and queue context spatially. Toggle between queue concentration, interconnection queue, and renewables layers to see a different slice of the same public infrastructure context. The legend in the bottom-right corner updates to match the selected layer and collapses out of the way when not needed. Queue concentration is a proxy based on active queue-project count near a substation; it is not a measured grid condition. Queue status reads active, operational, suspended, or withdrawn; renewables size each point by capacity in MW. Transmission stays a neutral color across every mode: line width tracks voltage class, opacity tracks whether in-service status is actually known, not assumed. Click any point for detail. Public infrastructure data does not establish the condition or status of a private project, and queue position is context, not destiny.

The project as a dependency system.

Cascade organizes milestones by workstream and records explicit dependency edges, lag, planned and actual dates, deadlines, and consequences. The operational model is built from named project records: milestones, dependencies, deadlines, and evidence. A dependency is not treated as true merely because it is plausible; source, confirmation state, project scope, and scenario status determine whether information may support an operational conclusion. Proposed or simulated changes must remain distinct from committed project state.

The intervention before the explanation.

Anticipate presents a recommended intervention, expected impact, causal chain, timing, and confidence, reasoning over the connected project state rather than one isolated field. Public demonstrations use illustrative scenarios and public sources; they do not represent customer project data or autonomous project decisions. Cadentis is built toward staging proposed action for human confirmation, not toward acting on a project without a person in the loop: it does not sign agreements, certify controls, approve meeting records, or determine grant eligibility. Software proposes. Authorized people decide.