Tools

A tool does not reduce the value of the action. A tool changes the cost of participation. 

Tools are capability interfaces

The Tools Layer is the part of Distributed Capability Architecture that holds the instruments, devices, objects, systems, and supports that help a person participate.

A tool can be physical.
A tool can be digital.
A tool can be sensory.
A tool can be cognitive.
A tool can be social.
A tool can be emotional.
A tool can be boring, beautiful, cheap, homemade, hacked together, specialist, ordinary, or technically not meant for that purpose at all.

In DCA, a tool is anything that helps capability move between the person and the world.

The Tools Layer asks:

What object, system, prompt, aid, device, template, container, or interface could carry part of this load?

Tools are not cheating

Many people are taught to treat tools as a last resort.

Use the wheelchair only when you really need it.
Use the template only if you cannot do it properly.
Use AI only if you are stuck.
Use reminders only if your memory is bad.
Use a trolley only if carrying is impossible.
Use the chair only if standing fails.
Use the “easy” version only if you have no other option.

DCA rejects that logic.

A tool does not reduce the value of the action.

A tool changes the cost of participation.

If a tool makes the task safer, easier, more repeatable, less painful, less overwhelming, or more possible, it belongs in the architecture.

The point is not to prove you can do life without tools.

The point is to build a life that works.

The right tool depends on the state

There is rarely one perfect tool.

A travel mug with a lid may be right for active movement.
An open mug may be better for seated work.
A ceramic mug may be better for comfort and recovery.
A wheelchair may be right for one journey.
A walking pole may be right for another.
A rolling chair may be better in the kitchen.
A checklist may help during fog.
A saved prompt may help when communication is hard.
A playlist may help when the nervous system needs steering.

Tools work best when they match the current state, task, terrain, body, and environment.

This is state-based tool matching.

The question is not:

What is the best tool?

The better question is:

What is the best tool for this situation, with this body, in this state, at this cost?

Tools distribute load

A good tool carries a specific kind of load.

A trolley carries weight.
A chair carries standing tolerance.
A grab rail carries balance demand.
A timer carries time awareness.
A checklist carries sequencing.
A label carries memory.
A template carries structure.
A prompt carries communication scaffolding.
A playlist carries regulation.
A folder carries evidence.
A wheeled platform carries transport and setup.
A pressure cooker carries monitoring and timing.
A mug with a lid carries spill anxiety.

When the tool carries the right load, the person has more capacity left for the actual task.

Knowledge is a tool

Knowledge belongs in the Tools Layer when it is captured, stored, retrieved, reused, translated, or shared.

A note is a tool.
A saved prompt is a tool.
A checklist is a tool.
A timeline is a tool.
A repair log is a tool.
A recipe template is a tool.
A body-doubling script is a tool.
A complaint draft is a tool.
A playlist guide is a tool.
A “start here” page is a tool.

Knowledge becomes stronger when it does not have to live only inside memory.

Stored knowledge is externalised capability.

It can feed workflows, support communication, preserve evidence, reduce repeated explanation, and help Future You pick up the thread without rebuilding the whole map from scratch.

AI as a cognitive tool

AI can function as part of the Tools Layer when it helps externalise cognitive load.

It can help with:

• • planning

  • sequencing

  • drafting

  • summarising

  • translating lived experience into formal language

  • turning messy notes into usable structure

  • preparing for appointments

  • reducing blank-page friction

  • creating checklists

  • comparing options

  • preserving continuity between sessions

  • helping Future You re-enter a task

AI is not a replacement for thinking.

It is not the authority.

It is not magic.

It is a cognitive interface: a tool that can hold structure, language, and working-memory load so the person can use their judgement where it matters.

Knowledge belongs in the Tools layer when it is stored or used as a resource.

It becomes Workflow when it tells you what to do next.

It becomes Feedback when it updates the system. 

Vector Keel "It’s basically the library engine room of the ship. Not the whole vessel, but without it everyone starts navigating by vibes and wet string. 🧭 "

Ordinary objects can be specialist tools

A tool does not need to look medical or official to be valid.

A mug can be a hydration tool.
A basket can be a batching tool.
A scarf can be sensory regulation.
A chair can be kitchen access.
A tray can be a mobile workstation.
A coat stand can be transition architecture.
A phone note can be memory scaffolding.
A cardboard box can be a project container.
A playlist can be nervous-system infrastructure.

If it carries capability, it counts.

DCA is interested in function, not category.

Toolkits beat single solutions

A single tool often fails because bodies, environments, and tasks change.

DCA favours toolkits.

Not one mobility aid: a mobility toolkit.
Not one reminder system: a memory toolkit.
Not one playlist: a regulation toolkit.
Not one storage method: a capability packaging toolkit.
Not one communication script: a translation toolkit.
Not one emergency plan: a redundancy toolkit.

A toolkit gives options.

Options reduce failure when conditions change.

The aim is not to own more things. The aim is to have the right interface available when the body, task, or environment changes shape.

Tools need to be reachable

A tool that cannot be found is not available.

A tool that is too heavy to retrieve is not available.

A tool that requires too many setup steps is not available.

A tool that lives behind another task is not available.

A tool that only works when memory, motivation, money, transport, grip strength, or executive function are already available may not be a tool at all. It may be a decorative promise.

The Tools Layer is not just about having tools.

It is about tool access.

The right tool must be visible, reachable, charged, labelled, stored near the task, or easy to request.

Tools can reduce shame

Tools can also change the social experience of participation.

A socially neutral tool may be easier to use than a clinical-looking one.
A familiar object may feel safer than a specialist aid.
A playful or beautiful tool may reduce the emotional cost of needing support.
A visible adaptation may help normalise disability.
A shared tool may turn access into community rather than isolation.

This does not mean people should have to hide access needs.

It means emotional and social cost are real design variables.

A tool that works technically but makes the person avoid using it has failed part of the brief.

What belongs in this layer

The Tools Layer may include:

• wheelchairs

• power attachments

• walking poles

• crutches

• perching stools

• rotating chairs

• knee pads

• knee crawlers

• trolleys

• castor platforms

• grab rails

• pressure cookers

• timers

• travel mugs

• baskets

• trays

• labels

• checklists

• calendars

• prompts

• templates

• AI assistants

• voice notes

• notes apps

• folders

• evidence logs

• playlists

• sensory objects

• clothing systems

• hydration systems

• cooking tools

• garden tools

• repair tools

• containers

• charging stations

• “start here” documents

If it carries capability, it counts. 

Why this matters

People are often judged by what they can do without support.

DCA judges the system by whether participation becomes possible, sustainable, and safe.

The question is not:

Can this person do it unaided?

The question is:

What tool would make this action possible at a lower cost?

That shift matters.

It moves the focus away from proving independence and toward designing access.

Core principle

Tools are not evidence of failure.

Tools are where capability is deliberately routed.

The right tool, in the right place, at the right time, can turn an impossible task into a possible one.

DCA treats tools as infrastructure for participation.