Construction · Contract administrationIn development
Construction
For commercial teams at tier 2 and tier 3 builders.
- Contract noticesIn development
- Notice status across projectsIn development
- Claims chronologyPlanned
Built environment AI
AI for the built environment.
Governed, and yours.
Agents that learn your procedures and ask before they act. Your know-how stays yours.
In development · Open for discovery
ModelsRented · swappable
- Frontier First release
- Open-weight Later
- Edge Later
Policy gatewayRedact · Route · Log
Your brainIn your tenant
- Procedures
- Corrections
- Evaluations
- Memory
- Audit trail
Exportable in an open format
Flag or draft Approved by a person
Construction first. Property and building operations next.Your brain Any model A person decides
01 / Industries
Built for the people who
build, own and run buildings.
Each industry has its own workflows, documents and rules. Construction is in development; property and building operations are being explored with teams now.
Property · Asset and lease managementExploring
Property and asset management
For asset, property and lease managers across commercial and residential portfolios.
- Lease critical datesExploring
- Lease obligations registerExploring
- Owner reporting draftsExploring
Building operations · Facilities managementExploring
Building operations and facilities
For facilities, building and operations managers running live buildings.
- Compliance calendarExploring
- Contractor follow-throughExploring
- Shift handoverExploring
Working somewhere else in the built environment? Tell us about the workflow.
02 / The idea
Own the brain.
Rent the reasoning.
Your rules, not generic prompts.
Agents work from your procedures, your contract settings and your templates, not a general assistant’s best guess.
Corrections that compound.
When your team dismisses or fixes a flag, the reason is kept. Each correction becomes memory, and a test the next model has to pass.
Every step on the record.
Each flag, draft, approval and model call is logged, so you can show how any output was produced.
03 / How it works
Flag. Decide.
Keep what you learn.
The same governed loop is designed to run every workflow. Only the sources, rules and templates change.
- 1
Sources arrive
Correspondence and records reach the agent through a dedicated mailbox or upload. Documents are treated as data, never as instructions.
- 2
The agent flags and drafts
Each output points to the exact excerpt and the rule it applied. Dates are calculated in code. Drafts use your templates.
- 3
You decide
Approve, edit, dismiss with a reason, or snooze. Nothing leaves without a person’s approval.
- 4
The brain keeps it
Decisions become memory and evaluation cases. Change models later and keep everything your team has taught it.
Swap the model. Keep the brain.
04 / What stays yours
The brain is yours.
So is everything it learns.
Designed to run in your own Azure tenant, in Australia East by default. Export the whole brain in an open, documented format at any time.
See how it’s built- ProceduresYour rules, in plain language and versioned.
- CorrectionsEvery fix your reviewers make, with the reason.
- EvaluationsTest sets from your own work that any model must pass.
- MemoryProject documents and history, searchable with citations.
- Audit trailAn append-only record of every flag, draft, decision and model call.
05 / Governed by default
Trust is designed in.
Not bolted on.
A person approves every action.
Agents flag and draft. They have no tool that sends anything outside your organisation.
Models decide nothing code can decide.
Dates, deadlines and rule checks are calculated deterministically and tested.
Every output shows its evidence.
Flags cite the source excerpt and the rule. Excerpts that don’t exist in the source are rejected.
Data is minimised before any model call.
Only the excerpts needed leave your tenant, with names pseudonymised. Inference location is stated exactly.
What ARK360 won’t do
- Stand in for legal advice or your team’s judgement.
- Send anything without a person’s approval.
- Train models on your data.
- Hide how an output was produced.
Built with perspective
Twenty years of delivery.
One narrow problem at a time.
ARK360 is an independent, founder-led business in Sydney. James Park brings around twenty years of technology delivery across property, construction and government.
The focus is narrow on purpose: agents that earn trust one workflow at a time across the built environment, starting with the notices that protect a builder’s claims.
Meet JamesStart with how you work today
One conversation.
No project data needed.
Tell us where dates, commitments and approvals slip through your team. We’ll tell you honestly whether ARK360 could help.
Book a discovery call30 minutes. No system access needed.
Prefer email? Write to James.
- 01
Walk us through your process.
How dates, commitments and approvals are tracked today, and who carries them.
- 02
Show us where it’s fragile.
A close call, a busy week, a handover. A description is enough; keep project data where it is.
- 03
Decide if there’s a fit.
If there is, we talk about a design partnership under a written agreement. If not, you leave with a clearer picture.
We’re looking for a design partner to run ARK360 on a closed or live project. That starts with a written agreement, and no real project data is used before it’s signed.
What is ARK360?
ARK360 is a Sydney-based business building governed AI agents for the built environment: construction, property and building operations. Each customer owns its brain: procedures, corrections, evaluations, memory and audit trail. A person approves every action. The first agent, in development, flags contract notice time bars for Australian builders.
Which industries does ARK360 cover?
Construction is first, with contract notices in development. Property and asset management and building operations are being explored in discovery calls; nothing has been built for them yet. Each industry page says which is which.
Can we use it today?
Not yet. ARK360 is in development, and the first release is being built and tested on a fictional project. The examples on this website use fictional data. We’re holding discovery calls now and looking for a design partner.
What does “own the brain” mean?
The things that make an agent useful to you are designed to live in your environment: your procedures, your reviewers’ corrections, your evaluation sets, project memory and the audit trail. They can be exported in an open, documented format, and they stay yours if you change models or stop using ARK360.