Weighted on arrival
Creation and reassignment each queue a scoring job, so Intrinsic Load lands with the task instead of being negotiated in a planning meeting.
Built for engineers who live in flow state.
Replace arbitrary story points with Intrinsic Load tasking, keep Git-synced living docs beside code, and verify every AI action before merge.
Story points don’t measure difficulty. Cognitive load does.
Built for engineering teams who value deep work over dashboard theatre.
Cognitive Load Taskboard · Live Mental Capacity Gauge
AR
Alex Rivera
Principal Systems Eng
Load Score:64%
ER
Elena Rostova
Full-Stack Developer
Load Score:42%
MV
Marcus Vance
Infrastructure Lead
Load Score:89% (Shielded)
Incoming Unweighted Backlog · Click to Route by Real CapacityFormula: CW = IL + EL
See real cognitive weight, not just card status
Every task carries an AI-computed Intrinsic Load score derived from task complexity and historical churn—protecting engineers from overload and surfacing real team capacity.
Cognitive load, in the loop
Watch a task get scored, a doc rewrite itself, and a merge wait on a human signature — the same loop, end to end.
Docs that keep up
A milestone completes and the project doc folds the event in on its own — no one opens the wiki to update it.
Held for a signature
High-risk AI writes, like publishing docs or triggering a deploy, pause for review before they ship — the same ritual applied to code.
Knowledge that lives beside the code, not in a stale wiki.
Most internal documentation dies the moment code is merged because developers refuse to maintain a disconnected wiki.
Lornian’s living docs automatically fold milestone completions and deployment logs into project documentation. Connect the repository once and the knowledge base drafts itself from the code, so the rationale behind a decision is still there when someone goes looking for it two quarters later.
Where the load number comes from
Story points are a group negotiation. This is a measurement with inputs you can inspect.
The task is scored on arrival
Creation and reassignment each queue a scoring job, so the weight lands before the task does. Nobody is estimating anything in a planning meeting.
Your scope is a sentence you wrote
A fluid scope is a short, human-written note about what you are actually holding this week. It outranks your job title in every routing decision.
Load is a sum, not a count
Active weights aggregate per member and recalculate across the workspace on every task change. Six small tasks and one large one are not the same number.
Crossing the line changes behaviour
Passing your threshold flips deep-work protection and broadcasts it. The team can see you are full without you having to say so.
Protect your team’s flow state
Bring Cognitive Load tasking, living docs, and Co-Sign verification to your engineering stack.