Loegos

Loegosdesktop-firstassembly system

System thesis

Less dashboard. More object.

The workspace should not feel like files plus chrome. It should feel like one assembled object gaining reality as sources, operator blocks, and receipts press it into form.

seed as objectblocks as primitivessolidity over rainbow statesettlement earns trust

Object preview

Declared0 receipts

Wireframe seed

Aim exists. The object is visible, but reality has not answered yet.

Grounded3 receipts

Partial solidity

Sources and early returns give the shape weight without pretending it is finished.

Sealed14 receipts

Object becoming real

Receipts have filled enough of the shape that the next move can be made honestly.

System pillars

The product only wins if the theory stays visible in the interface

Object

One box, one seed, one changing shape

The seed is not a note beside the work. It is the work becoming legible to itself across phone capture, desktop assembly, and proof.

Language

Words behave like assembled parts

Operator sentences are small enough to carry, but strong enough to change what the user does next.

Proof

Settlement earns solidity

Receipts do more than log history. They turn wireframe intention into something the box can stand on.

Operator blocks

Language becomes a native interaction material

In Loegos, sentences are not garnish. They are small assembled parts that can be carried, staged, rewritten, and pressure-tested.

Aim block

Open a sourdough bakery in Cobble Hill by Q1.

Issues the invoice. It names what reality would have to answer.

Ground block

Lease research for 3 locations. Cost estimate verified.

Adds material with provenance instead of vague context around the goal.

Bridge block

Funding gap remains $40K. Next move: lender shortlist.

Turns diagnosis into a runnable next move rather than another discussion loop.

Seal block

Startup cost estimate verified. Receipt sealed Mar 8.

Marks the point where a claim survived contact and earned solidity.

Operator chain

Aim

Ground

Bridge

Seal

Settlement

Trust is a settlement outcome, not a decorative state

The shell shows compact signals. Rich trust only appears where the user expects proof: Operate, receipts, and the seed's solidifying edge.

Invoice

A declaration opens an account with reality. The system frames what would count.

Move

The user acts. The box should preserve intention, cost, and chosen direction.

Return

Reality answers back through friction, witness, or external evidence.

Receipt

That answer becomes a portable proof object with provenance attached.

Seal

Trust is earned only after settlement. The object becomes more solid here.

Foundations

One visual system, with clear jobs for color, type, and motion

Palette

Canvas

Whole-app ground and negative space.

#0d0e10

Shell

Main workbench plane and structural surfaces.

#121315

Raised

Focused work regions that need separation, not decoration.

#1b1f24

Action blue

Identity, active states, selected controls, and the one primary action.

#5ea7ff

Verified

Settlement succeeded and the proof can bear weight.

#7fd9a0

Partial

Promising, cooling down, or still awaiting stronger contact.

#f0bf69

System laws

Assembly depth is shown through fill, density, and seal marks.
Green, amber, and red never become brand language.
Monoline icons stay in a 16 to 18 px band for routine controls.
Mono is for tags and proof metadata. Sans is for the work itself.

Control family

Seed prompt

VerifiedCooling downOpen

Navigation grammar

The tool should navigate the way assembly itself moves

Navigation is not a separate decoration layer. It should follow the same phase logic as the work, getting louder or quieter depending on what the user is assembling from the first field capture to the sealed receipt.

Capture

Take in the world

see -> capture -> file to box

Phone intake should be immediate and low-friction. A photo, voice note, or pasted link enters the same object the desktop later shapes.

Think

Read the source

source -> listen -> select

The document owns the screen. Navigation quiets down to source switching, playback, and Seven support.

Create

Shape the seed

staging -> rewrite -> compare

The tool becomes tactile here. Navigation pulls the seed, staging, and editable blocks into one working posture.

Operate

Read the box

run -> diagnose -> decide

Operate should feel singular and decisive. The shell sheds side-noise and frames one honest read.

Proof

Inspect the return

receipt -> witness -> seal

Proof is not another editor. Navigation shifts into ledger mode, where return, witness, and next move become legible.

Cross-device posture

Mobile and desktop should feel equally good, not merely compatible

Equal quality does not mean identical screens. It means each device gets the right version of the assembler tool while preserving one shared object model.

Phone

Field capture and fast orientation

capture -> file -> glance -> move

The phone should be immediate enough to pull out on the road, take a photo, drop a voice note, and see the current seed without friction.

Desktop

Deep assembly and proof work

compare -> rewrite -> operate -> inspect

Desktop earns its density by letting the user compare sources, shape the seed, run Operate, and inspect receipts with more context at once.

Shared laws

One object across both

same nouns -> same signals -> same box

The box, seed, receipts, and trust signals should not rename themselves between devices. The posture changes, not the product language.

Workspace proposition

The shell should frame the object instead of burying it

Create

Current seed

One object, multiple views3 receipts sealed

Open a sourdough bakery in Cobble Hill by Q1.

Lease research for three locations is sealed. Cost estimate verified. Funding gap remains open. The next move is a lender shortlist.

Aim

Ground

Bridge