Why InventArch

A place for the project.
Not just its conversations.

InventArch connects the work people and agents do, the knowledge that informs it and the results they deliver. The aim is continuity: a project that can keep its understanding as it grows.

01
When the work grows

The hard part is
keeping the whole together.

A conversation can produce a good idea. A project needs to carry that idea through decisions, different kinds of expertise and things people actually use.

The café starts with a vision. That becomes positioning and a brand. The brand informs a menu and a website. The opening introduces planning, budgets and coordination. These pieces are connected even when different people or agents work on them.

Without a clear account of those relationships, the work can drift. Someone uses an earlier draft. An interpretation becomes an assumed fact. A new specialist has the output but not the reason behind it. InventArch gives those relationships a place in the project.

02
The practical distinction

Chat can be the interface.
The project is the foundation.

A question to askWhat InventArch makes explicit
What are we doing now?

A named piece of work, its kind, its method and its place in the larger goal.

What does it need to know?

Related sources and decisions, with the difference between evidence, interpretation and approval preserved.

Who is responsible?

The people, specialist agents and workspaces involved, with a defined part for each.

What came out of it?

A usable result, its checks and review state, and the work that can build on it next.

AI chat products can also use files, memory and tools. The distinction here is the connected project structure and selected methods around the conversation—not a claim that other tools can only produce text.

03
A connected foundation

Three parts,
working together.

A language for the relationships

Underneath InventArch are typed, linked records for things such as work, decisions, requirements and agent roles. Their identities and relationships can be checked. This is the technical foundation, rather than the main thing a new visitor needs to learn.

Kits for the method

A kit packages a way to work: steps, roles, references and checks. Different activities can use different methods while remaining part of the same project.

The Desk for the working view

The Desk brings a person’s conversation close to the map of work, knowledge, agents and decisions. It is the place to move between a focused session and the wider picture.

04
A useful way to explore

Follow this website.
Inspect the connections.

Project, workspace, Desk, kit—what is the difference?+

The project is the thing you want to achieve, such as making this website explain InventArch. A workspace provides a context for particular work: its knowledge, methods and roles. A project can draw on more than one workspace. A kit supplies a reusable method. The Desk is the app where you see and work with these connections.

This website is our own project. Its brief, private-agent draft, separate review and kept walkthrough come from a recorded session in the actual local Desk. The walkthrough and product captures then became inputs to the website you are reading.

Our own projectSee how this site came together

Follow the brief through Desk to a kept result, then into this website.

More possibilitiesExplore illustrative projects

The café, exhibition and team stories show how the approach can extend to other kinds of work.

Public foundationExplore the language and base tools

The public source repository explains the underlying records and methods.

Begin with the website story, or visit the Desk page to inspect the product captures. Personal-space sign-in is not open on this site yet; the entry page explains the planned access.