technology & authorship

show the working.

Five capabilities, with a person at the controls. These are accounts of studio builds, not evidence of client deployments.

perception

input
a shelf photograph
transformation
a model proposes an itemised inventory
output
ingredients to review
user control
consent before the photo read; correct what it sees
süschef: the build →

memory & retrieval

input
notes and authored links
transformation
indexing and similarity connect material for recall
output
notes returned with context
user control
write links yourself; inspect and export the notes
åsecond: the build →

decision support

input
a bank CSV
transformation
parse amounts, suggest categories and check duplicate rows
output
an approval queue before balanced ledger entries
user control
review and approve; invalid entries are refused
pacioli: the build →

spatial interfaces

input
notes, links or strokes
transformation
layout places relationships in a navigable space
output
a graph or drawing surface
user control
navigate, draw and select; a spatial view does not make an inference true
åsecond / Infinote: the build →

authoring

input
a sketch or scene description
transformation
authoring tools produce assets and scene instructions
output
an asset or a scene/interaction contract
user control
the maker chooses, inspects and exports; generated assets still need judgement
violet: the build →

reuse has a boundary.

åsecond brain layoutstudio wire’s brain view
Actual code reuse: the site imports åsecond’s layout through its source alias.
scene + interaction recipesite renderer
Authoring contract: a portable description consumed by the renderer, not a claim that all products share one runtime.

Consent, review, portability and legible decisions are shared design principles. They are not proof of a live data connection.

Planned connection: süschef receipt → pacioli import. The seam is designed; it is not wired. No automatic kitchen-to-ledger sync is claimed.

what is ours. what isn’t.

The studio authors application code, visual systems, interaction rules, workflow contracts and its own research. Curation is the work of selecting and crediting; it does not transfer ownership of the selected material.

Models, hosting, libraries, typefaces, music metadata and credited recipes have their own owners and terms. Using a model is not owning it. An original interface is not a claim of patent protection.

For client work, the agreement names the deliverable code and designs, retained studio components, third-party licences, accounts and ongoing costs. Read how an engagement runs →