One coherent human loop.

01 / Nexus

Orient before acting.

Nexus brings current planning signals into one operating view and identifies where the next decision belongs.

• Does not invent a personal score when evidence is thin.
• Distinguishes missing signals from negative signals.
• Hands work to Creator, Timeline, or a guidance surface.

02 / Creator

Create with confirmation.

Creator turns a deliberate input into a preview, confirmation, receipt, and reversible result.

• Nothing is saved from the draft alone.
• The user reviews the exact object before confirmation.
• Receipts and undo preserve control after the save.

03 / Timeline

Place action in time.

Timeline projects scheduled work without treating every planned time as a missed deadline.

• Scheduled time and due time remain different facts.
• Planned action stays editable and reviewable.
• Outcomes can return to the reflection loop.

04 / Smart Planner

Work through the immediate situation.

Smart Planner uses the information provided for a bounded planning response and a concrete next move.

• Guidance is not represented as diagnosis or certainty.
• Follow-up language stays focused on the current planning problem.
• External generative explanation remains release-disabled.

05 / SI Console

Examine evidence and limits.

SI Console is a read-only evidence and recommendation surface for deeper investigation.

• Facts, calculations, inferences, and missing data stay distinct.
• Unsupported conclusions can be refused.
• Recommendations remain subject to user judgment.

06 / Trajectory

Compare scenarios, not destinies.

Trajectory exposes assumptions and uncertainty so a scenario can be examined instead of mistaken for a personal prediction.

• Scenario inputs and coefficients remain visible.
• Receipts support later comparison with observed outcomes.
• Precision is withheld when evidence cannot support it.

07 / Progression

Reflect without manufacturing identity.

Progression records evidence-backed movement and supports deliberate adjustment over time.

• Fresh users are not assigned an evidence-free archetype.
• Completion, deferral, and reflection can inform later planning.
• The person can correct what the system got wrong.

Product model, not a screenshot. This page explains responsibilities and trust boundaries. It does not present staged interface art as proof of a shipped runtime state.