01 / Identify
Identify the person, client, and Job.
Dowelify resolves the authenticated person, their participation, and the exact Job before compiling what the connection can see or do.
Connectors / Many ways into the Job
Every doorway meets the same Job.
Work can begin at the equipment or in Dowelify, and a pilot can map a bounded link to a customer system. People and instruments add observations. Compatible AI applications can receive an authorized view. Every contribution meets the same Job without turning its interface into a second record or authority.
The conversation may move. The Job does not fracture. Every connection keeps its source, scope, and authority visible.
One Job · scoped exchange · human authority- 01At the equipmentA printed Dowel or manual selection locates the Subject and its work.
- 02People in DowelifyReport, investigate, record, review, and decide from the same Job.
- 03Customer systemsA pilot can test a bounded ticket link after that path is configured and proven.
- 04Instruments + sourcesManual Measurements and references retain their method, source, time, and limits.
- 05AI workspacesModel Context Protocol (MCP) is the standard doorway for an authorized read-only Job view; human authority stays in Dowelify.
The operating map
Everything meets at the Job.
People and physical entry meet the Job now. Manual instruments, a scoped customer-system pilot link, and compatible AI access meet it only through their governed boundaries.
A Dowel locates the equipment. A Measurement records an observation. A person accepts the Result.
Founding pilot / Reported-leak loop
A leak report moves without splitting the record.
From the first report at the equipment to the technician's readings and the manager's decision, each participant meets the same Job through the interface suited to their part of the work.
Founding pilot / Proposed operating loop
The round trip the pilot is designed to test.
- 01Locate
A printed Dowel or ordinary report identifies the equipment and reporting path.
- 02Open
Dowelify opens the canonical Job with the location and report.
- 03Link
If scoped and configured, the pilot links a customer ticket to the Need without creating another evidence history.
- 04Investigate
The technician adds observations, photo references where supported, and manual moisture readings.
- 05Explain
An authorized AI reads the same Job through MCP and can draft a summary outside the record.
- 06Decide
The named manager accepts the Result or requires the next action. The pilot goal is a bounded return of accepted status, summary, and record link.
How each connection works
Useful context crosses. Authority does not.
02 / Compile
Compile the smallest useful slice.
The connection exposes only the Job material needed for the request, with its version, provenance, limitations, and authority boundary intact.
03 / Exchange
Keep every exchange attributable.
Reads, observations, and bounded events retain their source and role. The connection is transport; it does not become a second record or authority.
AI workspace / Read-only pilot
AI receives an authorized view through MCP. Human authority remains with people.
Model Context Protocol, or MCP, is the standard doorway compatible AI applications use to receive an authorized view of the Job. The current connection is read-only and bounded to the Job material authorized for the request. It cannot perform, verify, accept, sign, release, or pay.