coap.TREN

Architecture × Technology

A studio that runs on its own protocol.

Our projects share one MCP layer. On top of it we build the tools that architecture, interiors, project management and operations work from: CO Tower and COAP Panel.

CO monogram rendered as a dot matrix

The idea

COAP is also a protocol.

The name reads two ways: Ceren × Orhun Architectural Partners, and Constrained Application Protocol. We decided to deserve the second reading. Underneath the studio runs a layer of our own that connects the work of four disciplines.

That layer is built on MCP, the Model Context Protocol: an open standard that lets AI assistants read from and act on real tools and data. Ours gives every project a single, structured memory.

The MCP layer

One layer under architecture, interiors, project management and operations.

Each discipline writes to the same layer and reads from it. A change made in one place is the change everyone else sees. On top of it we build the products our projects need.

ArchitectureDRAWINGS · AREAS · UNITSInteriorsROOMS · MATERIALS · FF&EProject managementSCHEDULE · TASKS · COSTOperationsCLIENTS · APPROVALS · FILESCOAP MCPMODEL CONTEXT PROTOCOLCO TowerPROJECT · SALES · ANALYSISCOAP PanelTEAM · CLIENT · OPERATIONSONE LAYER · ONE SOURCE OF TRUTH
Fig. 01 · The COAP MCP layer and the products built on it

Architecture

Drawings that answer questions

Areas, units and options are data, so they can be checked, compared and reported without redrawing.

Interior architecture

Rooms with a memory

Every room carries its materials, fixtures and furniture, so a selection is made once and followed through.

Project management

A schedule that knows the project

Tasks, dates and costs sit next to the drawings they refer to.

Operations

Clients inside the loop

Approvals, files and messages are recorded where the work is, not in a separate inbox.

Products

Two products, one foundation.

Both started as tools for our own projects. Both run on the same layer.

CO Tower

Project · Sales · Analysis

CO Tower

A project environment for buildings and developments.

The problem

Drawings, unit lists, areas and sales material live in separate files that drift apart.

What it does

Holds a project as one model: units, areas, options and analysis, with documents generated from the same data.

The result

One version of the project for the design team, the developer and the sales desk.

Open CO Tower
COAP Panel

Team · Client · Operations

COAP Panel

The studio's operating panel, with a team side and a client side.

The problem

Decisions, approvals and files scatter across chats, mail and folders, and nobody is sure which one is current.

What it does

Puts the project's rooms, selections, files and approvals in one place that both the team and the client can open.

The result

Fewer questions, faster approvals and a record of who decided what.

Open COAP Panel

Cause and effect

Why an architecture studio writes software.

Cause

Projects fail at the hand-overs

Between designer and site, studio and client, drawing and price. Information is retyped, and each retyping adds an error.

Decision

Remove the retyping

Put the project in one structured layer and let every tool, and every assistant, work from it.

Effect

Time goes back to design

Less chasing and checking. More hours on the part of the work that needs an architect.

Next step

Want this on your project?

We bring the layer and the tools with us. Ask us how it would work for your building or your team.

Work with us