Transparency.

When a client assigns a building to Wren, the agent is given access to the filings, inspections, permits, correspondence, drawings, and operating records that the client provides or authorizes Wren to fetch from the public record. Wren does not browse beyond the scope of the engagement and does not ingest buildings it has not been assigned to.

What Wren retains is the building’s record, the drafts produced against that record, the reviews performed against those drafts, and the reasoning that connects them. The record belongs to the building and travels with the engagement. Clients can export it in full at any time.

Every draft Wren produces is stored with the reasoning that led to it, the citations to the filings and codes it relied on, the reviewer who approved it, and the timestamp of that approval. Clients can open any draft and inspect the full chain without reconstructing it from logs.

Audit views are not a premium feature. They are the same surface Wren uses internally to present work for review, exposed to the client with the same fidelity. A licensed professional reviewing a building after a succession should be able to see exactly what was proposed, what was approved, and why.

Aedifice publishes research about how buildings age, how agentic systems behave inside licensed practice, and where the current generation of these systems falls short. Publications appear on the research hub with their methods, data, and limitations in the open.

Wren itself is released on a cadence documented in the release notes. Material behavior changes to the agent are announced before they take effect, and any change that affects how drafts are produced or reviewed is called out explicitly rather than bundled into a routine update.

When Wren produces an output that a reviewer catches as wrong, or that would have been wrong if it had reached a regulator, we record the event. Confirmed incidents that affect client work are communicated to the affected clients without undue delay. Patterns that emerge across engagements are reported in aggregate to the broader user base so reviewers know what to watch for.

Near-misses are treated as primary signal. An agent that almost made a material error teaches us as much as one that did. We do not under-report near-misses to preserve a cleaner narrative about the product.

To report a transparency concern, a miscommunication, or a missing disclosure, write to transparency@aedificeai.com. For security-specific reports, the responsible disclosure address is listed on the security page. Reports are reviewed by a named individual, not a ticket queue, and an acknowledgment is returned within one business day.