The Shape of the Work

Lately, I have been building the work and the conditions that let the work continue.

Websites, design studies, poems, torn paper, research, archives. Alongside them: the systems that help me find something again, carry a decision forward, collaborate with an agent, or recognize that a question from one project has wandered into another.

Several things are developing at once.

Design Intelligence. File Zero. Mulcher. A shared operating layer I have been calling Core. Torn Frames. The writing here at ndcodex. An expanding inquiry into spiritual mechanics and the broader question of how things work.

They are not all the same project.

But their relationships are becoming easier to see.

A question keeps appearing underneath them:

How do we make what we learn available to what we do next?

Not just stored.

Available.

Something we can find, understand, question, use, revise, and return to the work.

That is a good place to begin this roundup.

Design that remembers

A design project produces more than its deliverables.

There is the finished website, certainly. But there is also everything discovered while making it: why one arrangement worked, where the navigation became confusing, what a particular type relationship accomplished, which assumptions survived contact with actual content.

I want more of that learning to remain accessible.

That is the work taking shape around Design Intelligence.

The ambition is not simply a larger collection of references. I already know how to collect things. The harder question is what happens after collection.

Can an observation become useful intelligence?

Can a successful pattern retain the context that made it successful?

Can a future project inherit a lesson without inheriting an entire previous project’s appearance?

An editorial study, for example, might begin with the relationship between an eyebrow, headline, introduction, paragraph, and action. But the useful learning is not limited to their sizes. It includes sequence, emphasis, pacing, content length, image behavior, and the circumstances under which the arrangement starts to fail.

I want to preserve those relationships.

Not just the screenshot.

The screenshot shows what happened. The study should help explain what was working.

Design Intelligence is my attempt to give that learning somewhere to accumulate without prematurely declaring every discovery a rule.

File Zero: a place to begin

Within that work, File Zero is becoming the proposed starting environment for design in Figma.

Not a finished aesthetic waiting to be applied to everything.

A prepared place to work.

Responsive starting structures. Adaptable parts. Clear naming. Space for references and studies. Ways to distinguish an experiment from something ready for review. Conventions that help a human or an agent enter the file and understand what is happening.

I do not want to solve the same basic setup problems every time a new project begins.

I also do not want efficiency to become an excuse for making the same website repeatedly.

The distinction matters:

Reuse the support structure. Keep the design available to discovery.

One useful frame has been the file as both shop floor and exhibit.

On the shop floor, the work can be unfinished. Studies sit beside alternatives. Questions remain visible. Something can be promising without being approved.

The exhibit is where the work becomes legible to someone who has not been standing beside the machinery all day.

What are they looking at?

What decision is being requested?

What is settled?

What is still open?

A review should not require someone to excavate the designer’s entire working memory.

The same applies to feedback. I want comments and decisions to become part of the project’s retained intelligence, rather than a conversation that disappears once the next screen is drawn.

And underneath all of this is the question of when to harden.

When does a useful arrangement deserve to become a reusable component?

When is a preference mature enough to become a convention?

When should a promising idea remain a study?

Part of the operator’s job is knowing when to leave something soft.

Mulcher and the front door

Before something becomes intelligence, it often arrives as a fragment.

A screenshot. A paragraph. A strange observation. A link with three words attached. A question that does not yet know which discipline it belongs to.

Mulcher is the developing intake and processing project around that material.

One of the simplest decisions has also been one of the most useful: give incoming material a clear front door.

The Jar is an inbox outside the curated vault.

Dropping something into it does not make that thing important, verified, or permanent. It means the material has somewhere to land without requiring me to finish thinking about it first.

Selection and ingestion are separate acts.

That is where a receipt becomes meaningful: what was selected, where it went, what was extracted, and what remains unresolved.

Collection is not endorsement.

Extraction is not verification.

And a compelling observation does not become established knowledge merely because an agent can write a beautiful paragraph around it.

The aim is to move from accumulated material toward usable understanding while keeping the path between them visible.

Some fragments will become studies. Some will support an existing question. Some will expose a new one.

Some should simply remain fragments.

The person beneath the systems

These projects also keep revealing the need for a shared operating layer.

I have been calling that layer Core.

The basic distinction is that my domains of work are not the same thing as the infrastructure that supports them.

Freelance work has its own responsibilities. Art has its own purposes. Personal projects have theirs. This journal is not merely a marketing department for any of them.

Shared infrastructure can serve those domains without owning them.

That includes the practical material: project orientation, working conventions, device roles, storage, handoffs, archives, and the information an agent needs to collaborate without requiring a complete reintroduction every time.

An agent needs more than a task.

It needs to know what kind of work it has entered, what it is allowed to change, what counts as evidence, what remains undecided, and where human judgment belongs.

I am trying to make those conditions more explicit.

Not to remove myself from the work.

To spend less of myself repeatedly explaining where the work is.

Some of this is already being exercised in live projects. Some is still proposed architecture. I want that distinction to remain visible.

A diagram of an operating system is not proof that it operates.

Eventually, the thing has to help on an ordinary day.

Torn Frames: the object keeps its history

The art practice offers another version of these questions, but it deserves to remain art.

Torn Frames is developing around torn paper, salvage, singular objects, and the archive that can hold them.

Here, preservation is not simply a matter of keeping the file.

What is the object?

Where did the material come from?

What happened to it?

Which marks belong to its previous life, and which belong to the act of making this one?

How much do I know, and where should the record say that I do not know?

I am interested in documentation that gives an object presence without pretending to explain it away.

A title, a date, a material description, a condition note, a fragment of provenance. These can create a way into the work without closing off the encounter.

The frame matters too.

It can contain the image, interrupt it, or become part of what the image is doing. The boundary is not always neutral.

There is a relationship here to interface design and information architecture. But the relationship does not make the artwork a design exercise.

The object does not owe the system a lesson.

Sometimes the system’s entire job is to let the object remain strange.

Language is also a working surface

The poetry continues alongside the architecture.

Sometimes before it.

A line arrives before there is a category for it. A phrase catches something the more formal language has been circling. Rhythm finds an opening that explanation could not.

I work through fragments, line by line, and eventually through the larger act of stitching.

Spelling, punctuation, capitalization, spacing, breaks. Every character can change the pressure of the thing.

This is part of why I keep returning to raw markdown. I want the text close enough to touch. I want to see what has actually been placed there.

But the writing is not just another material waiting to be processed.

A poem is not an inefficient research note.

Its uncertainty may be essential. Its contradiction may be the point. Its force may depend on refusing the tidy explanation I could produce afterward.

Using language to unbury me.

That phrase names something the diagrams do not.

There is a person underneath the systems, and language is one of the ways that person remains present.

Not everything I write needs to become doctrine, a framework, or a reusable asset.

Some of it needs to speak.

Some of it needs to make a sound large enough to stand inside.

The shape of things

The spiritual mechanics study belongs within this larger practice of inquiry.

It is one branch of a broader fascination:

How does a thing work?

What are its structures, postures, states, functions, exchanges, thresholds, and failures?

What does it do?

What do people say it does?

What can we observe, and what are we interpreting?

In the spiritual study, that means examining proposed spiritual anatomies, practices, experiences, symbols, and forms of authority. It means placing theological language beside other ways of studying human life without pretending they are interchangeable.

But the same habit of inquiry extends into design, behavior, culture, institutions, technology, ethics, and justice.

A navigation system proposes a way through something.

An institution organizes participation and authority.

A ritual gives an action a setting and a sequence.

A poem arranges attention through language.

These are not equivalent mechanisms. They are different places where questions about structure and behavior become useful.

I am not trying to force them into one master explanation.

I am trying to improve my ability to notice what is happening.

Continued understanding, rather than full knowledge.

The distinction keeps the work open.

Cross-informed, not collapsed

One of the most promising questions has also been one of the simplest:

How do these all inform one another?

What might an editorial study reveal about the presentation of research?

What might archive practices teach a design system about provenance?

What might poetry expose about pacing, emphasis, and omission?

What might an inquiry into authority help me notice about permissions in an agentic workflow?

These are invitations to investigate, not declarations that a correspondence has been proven.

The individual stores need to retain their sovereignty.

A theological interpretation should not quietly become a scientific finding. A design preference should not acquire the authority of a universal law. A powerful metaphor should remain distinguishable from evidence.

I want to mark the crossings without erasing the borders.

That suggests a useful kind of record: not only what we know, but which relationships are worth examining next.

A store of golden queries.

Questions specific enough to pursue and open enough to reveal something unexpected.

Sometimes the next useful act is not a grand research expedition.

It is a small, well-aimed inquiry that reveals whether a thread is worth following.

The return is part of the work

All of this needs an ethic beyond accumulation.

More files, more agents, more categories, and more automation are not sufficient evidence that something useful is happening.

The system has to return something.

A clearer decision. A stronger piece of work. Less repeated setup. An observation that would otherwise have been lost. A handoff another person can actually use.

Room to think.

Room to stop.

I do not want infrastructure that recruits the entire practice into maintaining the infrastructure.

The machinery serves the work.

The work does not exist to keep the machinery busy.

The creative ethic I keep returning to is:

Dwell. Perceive. Discern. Make. Return.

Return means bringing something back from the encounter.

It means allowing the result to improve the conditions of the next attempt.

It also means returning to the people affected by the work, to the question that justified the effort, and to the world beyond the system.

A loop that never returns anything has become a demand.

What this place is for

ndcodex is where I can keep a public record of these developing relationships.

Not only finished explanations.

Field notes. Poems. Studies. Objects. Questions. Working models. Revisions. Occasional evidence that an earlier conviction needed to be dismantled.

I do not need everything to resolve into one identity before it can belong here.

The designer can remain a designer.

The poet can interrupt.

The artwork can refuse the framework.

The research can correct the story.

The person can decide that the system needs to be smaller.

What connects these things is not that they all perform the same function.

It is the practice of paying attention, making something from the encounter, and remaining available to what the result teaches.

So that is the current shape of the work.

A design practice learning how to remember.

An archive learning how to preserve context.

A collaboration learning how to carry judgment without pretending to replace it.

A collection of questions learning where to look next.

And language, still moving through all of it.

Some of the structure is becoming clear.

Some of it is still a pencil mark.

The next piece of work gets to tell me what needs redrawing.