Workstream

LOKE/KORA Product Definition

Define the first executable product surface for withLOKE.

Context Brief

Since your last session...

Since the last session, the product definition package and KT marching orders were established as the governing inputs. Week 1 is now focused on making the static product shell visible, calm, and navigable.

Suggested next focus

Build the Workstream Index and first Workstream Detail experience using mock data before adding persistence or AI behavior.

Continue Work

Open Loops Preview

in-progress Create Week 1 static shell
Build the entry page, Workstream index, Workstream detail page, and core static views.
open Avoid scope expansion
Keep the prototype focused on product shape, not database, integrations, auth, or live AI behavior.
deferred Prepare for Vercel Analytics
Add analytics later at the layout level after the static shell is stable.

Recent Decisions

final Use withLOKE as product-facing identity
withLOKE frames the experience as working with LOKE, not using a generic tool.
final Week 1 uses mock data first
The first build should prove product shape before persistence, AI, integrations, or browser capture.

Sources Preview

document LOKE Control Tower KT Marching Orders
Defines how the implementation workstream should operate and what Week 1 must deliver.
document LOKE/KORA v0.x Product Definition Package
Defines what withLOKE is, what belongs in v0.x, and what must remain out of scope.

Core Views

Focus · Context · Map · Open Loops

Focus View

I can think here.

Current focus

Build the Workstream Index and first Workstream Detail experience using mock data before adding persistence or AI behavior.

This is the calm working surface for the Workstream. In Week 1, this area is static. Later, Jorge will be able to write, organize, apply Thinking Actions, capture decisions, and close the session with a continuity summary.

Thinking Actions

Suggested refinement appears here. Jorge can insert, save, convert, or dismiss before anything changes.

Context View

What this Workstream knows.

Context Notes

summary Core product loop

Open → Orient → Start → Work → Think → Capture → Recall → Close → Resume.

note Continuity, not storage

The product should preserve relationships between work, sources, decisions, open loops, and context.

Sources / References

document LOKE Control Tower KT Marching Orders

Defines how the implementation workstream should operate and what Week 1 must deliver.

document LOKE/KORA v0.x Product Definition Package

Defines what withLOKE is, what belongs in v0.x, and what must remain out of scope.

Decisions

final Use withLOKE as product-facing identity

withLOKE frames the experience as working with LOKE, not using a generic tool.

final Week 1 uses mock data first

The first build should prove product shape before persistence, AI, integrations, or browser capture.

Map View

What connects to what.

Week 1 shell connects to v0.x scope

The static shell should express the approved primitives without making them fully functional yet.

Context BriefFocus ViewQuiet RecallOpen Loops

Open Loops View

Action memory, not project management.

in-progress Create Week 1 static shell

Build the entry page, Workstream index, Workstream detail page, and core static views.

open Avoid scope expansion

Keep the prototype focused on product shape, not database, integrations, auth, or live AI behavior.

deferred Prepare for Vercel Analytics

Add analytics later at the layout level after the static shell is stable.