archi.sulerr

Trust is built from specifics, not slogans.

Below: the named roles in your project, where your files live, what the AI is and is not allowed to do, our refund commitments, and the sign-off chain that ends with you handing a signed package to your municipality.

Who does what

Three named roles. Each owns one part of the chain. No silent hand-offs.

AI working draft (Claude Opus 4.6)

+ responsibilitiesReads your brief; produces a first-pass concept with room areas, code-compliance preview against the local building code (Bbl / ДБН / WT / GEG), and an indicative cost band. Flags every cost and regulation number as indicative.

− limitsDoes not sign anything. Does not carry professional liability. Does not replace site visits, structural calculation, or municipal consultation. Cannot certify a permit.

In-house engineer review

+ responsibilitiesA named engineer reviews the AI draft against your brief, fixes scope mismatches, and validates the JSON-Schema output. Confirms that the layout is buildable and that the indicative numbers are plausible for your plot.

− limitsNot a registered architect. Cannot sign a Tier 2 permit package. Cannot stamp drawings for submission.

Registered architect sign-off (Tier 2)

+ responsibilitiesVerifies the package against the local register's standards (SBA / НААУ / IARP / Architektenkammer), refines what is needed, and applies the signed-and-stamped sign-off you submit to the municipality. Carries the professional liability and insurance for that signature.

− limitsSigns only what they have personally verified. Does not certify structural Eurocode calculations (those stay with a Constructeur / structural engineer). Does not supervise the build site.

Data handling

Where your files live, who can open them, and how long we keep them.

  • Files are stored on a single EU-region host (no third-party CDN handles personally identifiable information). Briefs and AI outputs are written to local disk as JSON; no PII is sent to analytics or ad networks.
  • Unconverted briefs (Tier 0 working drafts that never proceeded to a paid tier) are deleted after 90 days unless you ask us to keep them longer.
  • Signed Tier 2 packages are retained for 7 years, as required by the professional-archive obligations of the signing architect's register.
  • Three named roles see your data: the in-house engineer reviewing your draft, the partner architect signing your Tier 2 package, and the site owner for security/incident response. No outsourced support, no off-shore review.
  • You have the GDPR rights of access, rectification, portability, restriction, objection and erasure under Art. 15-22.
  • You can request immediate deletion of your account and all attached drafts from /lk/data — confirmed within one business day.

AI guardrails

Concrete limits on what the AI can do — implemented in code, not as a promise.

  • Model: Claude Opus 4.6 (Anthropic), accessed over EU-region endpoints. Model version is logged with every draft so you can reproduce or audit the output later.
  • Every AI output is validated against a JSON-Schema (see outputValidator.ts). Outputs that fail the schema are rejected, never shown to you as a finished draft.
  • A forbidden-phrase list (LEGAL_FORBIDDEN.json) blocks claims we cannot honestly stand behind — fabricated counters, fake testimonials, guarantee language we can't support.
  • Every cost figure and every regulation citation is labelled indicative until a registered architect has verified it in the Tier 2 review. The AI does not silently round numbers.

AI disclosure & EU AI Act

Refund & commitment policy

What we owe you, per tier, if the deliverable does not match the engagement.

Tier 0 (free working draft)Free. No card on file. No refund needed because no money is taken. If you don't like the draft, simply don't continue.
Tier 1 (engineer review)If the engineer review uncovers a scope mismatch that we did not catch up-front, you get a full refund within 14 days. EU consumers also keep the standard 14-day right of withdrawal under consumer law.
Tier 2 (architect sign-off)If the signed package fails permit submission for a fixable reason within 30 days of delivery, we revise and re-sign the package at no extra cost — or refund the architect-sign-off fee. Refunds do not apply to changes you make to the brief after sign-off.

The sign-off chain

End-to-end accountability — every link is a named human role until the document is in your hands.

  1. Your brief → AI working draft (within 1 business day).

  2. Working draft → in-house engineer review (typically 3 business days).

  3. Engineer-reviewed draft → registered architect verification and sign-off (typically 2 business days).

  4. Architect-signed package → handed to you, with the architect's register entry and signature visible on the document.

  5. You submit the package to your municipality (Bouw- en Woningtoezicht / місцева влада / urząd gminy / Bauamt).

What we publish about ourselves

  • Uptime target: 99.5% (file-based ops on a single EU host). We do not invent five-nines we cannot deliver.
  • Response time: first human reply within one business day. AI working draft within 24 hours of submitting the brief.
  • Full data export of your account, briefs and AI outputs is available on request — machine-readable JSON, no PDF wall.
  • Every AI draft is stored with model name, version, prompt template ID, and timestamp so the output can be reproduced or audited.

Still skeptical? Start with the free draft.

Tier 0 is free, no card needed. You can read the full AI disclosure first.