Responsible Operation Policy.

This policy applies to every engagement on which Wren is assigned to a building, and to the research and product work that produces new behavior in Wren. It covers Aedifice employees, contractors, and the licensed partners we engage to open new jurisdictions.

Where a specific client contract sets a stricter standard than this policy, the client contract governs. Where this policy sets a stricter standard than the jurisdictional minimum, this policy governs.

Every output Wren produces is routed to a licensed human before it leaves the building’s record. The reviewer is named, their license recorded, and their approval captured alongside the draft. Wren does not file, submit, attest, or close work on its own.

Review cannot be bypassed by configuration. Workflows that would require bypassing review to deliver on a timeline are, by policy, workflows we decline rather than workflows we accelerate.

Aedifice does not open a new jurisdiction until two conditions are met. First, the relevant rules for that jurisdiction are modeled to a standard that a licensed local professional can verify. Second, a licensed local partner is engaged, named, and accountable for the practice in that jurisdiction.

Marketing a jurisdiction before these conditions are met is not permitted. A waitlist for a future jurisdiction is labeled as such and does not represent an active engagement.

Aedifice commits to pulling back from a jurisdiction, a workflow, or a product surface under the following conditions: a confirmed pattern of Wren producing outputs that a responsible reviewer cannot check in time to matter; a regulatory change that the current rule model cannot accommodate; a material security incident that affects the record of work; or the loss of the licensed local partner with no replacement in place.

A halt is announced to affected clients before it takes effect where possible, and immediately otherwise. The scope and expected duration of the halt are published, and the conditions for resumption are stated in advance.

This policy is reviewed on a published cadence by a governance group that includes licensed professionals working on the platform, a representative from operations, and a representative from research. The group reviews incidents, near-misses, halt conditions, and proposed changes to the policy.

Meeting summaries are published. Individual incident reports are retained internally for the period required by applicable professional standards, and summarized in public releases where it is responsible to do so.

Aedifice commits to notifying affected clients of confirmed incidents that touch their building records or their draft work within the timelines set out in the client contract, and in any case without undue delay. For incidents that affect the broader user base, a public-facing summary is published on the research hub once the affected clients have been informed directly.

To report an incident, write to incidents@aedificeai.com. Security-specific reports should follow the responsible disclosure process on the security page.