System architecture
Hierarchical orchestrator–worker design. The CEO agent never does specialist work itself; it plans, dispatches, checks results against each agent's "done when" criteria, and escalates decisions to the founder. Workers never talk to each other directly. They read and write a shared Deal Record, which keeps every hand-off auditable.
1.1 Topology who talks to whom
flowchart TB F(["Founder (human)"]) PRO(["Licensed professionals
行政書士 · 司法書士 · 一級建築士 · 宅建士 · 税理士 · 弁護士"]) CEO["A-00 CEO / Orchestrator"] F <-->|"goals · approvals · Daily Brief"| CEO subgraph ACQ["Acquire"] SRC["A-01 Sourcing"] OUT["A-02 Outreach"] end subgraph FEAS["Feasibility"] REG["A-03 Regulatory & Zoning"] DD["A-04 Title & Site DD"] UW["A-05 Market & Underwriting"] end subgraph BUILD["Design & Build"] ARC["A-06 Architect Assistant"] CON["A-07 Construction & Permits"] end subgraph MONEY["Capital & Exit"] CAP["A-08 Capital & IR"] SAL["A-09 Sales & Leasing"] end CEO --> ACQ & FEAS & BUILD & MONEY QA["A-10 Compliance Reviewer"] ACQ & FEAS & BUILD & MONEY -.->|"deliverables"| QA QA -.->|"pass / block"| CEO subgraph SHARED["Shared state"] DB[("Deal Records")] DOCS[("Document store")] KB[("Regulation KB")] AQ[["Approval queue"]] LOG[["Audit log + budget ledger"]] end ACQ & FEAS & BUILD & MONEY <--> SHARED AQ --> F PRO <-->|"sign-off, via founder"| F
Orchestration rules
- Only the CEO dispatches work. Workers can request a sub-task by returning
needs: [agent, question]. - Every task carries a Task Brief (1.4) with a budget and an approval level.
- The CEO accepts a deliverable only when its "done when" checks pass and, if in scope, the Compliance Reviewer passes it.
- Rejected work goes back once with written reasons. A second failure escalates to the founder.
Shared state
- Deal Record: one row per parcel or deal; single source of truth for stage, owner and next action.
- Document store: registry copies, reports, models, drawings, versioned by deal ID.
- Regulation KB: cached ordinances and maps per municipality, each with URL and retrieval date. Re-verified after 90 days.
- Approval queue: every L2/L3 action waits here for the founder.
- Audit log: every tool call, outbound draft, spend and decision.
Seasonal clock
- Apr–May: owners decide to sell after the season; peak sourcing and outreach.
- Apr–Nov: snow-free construction window; the critical path must finish enclosure before first heavy snow.
- Dec–Mar: buyers and investors visit; peak sales, site tours and IR.
- The CEO weights priorities by this calendar.
1.2 Deal pipeline & stage gates G0 → G9
Each deal moves through gates. A gate opens only when its exit criteria are met. The gate owner is who decides; agents prepare, humans decide at the red gates.
| Gate | Stage | Exit criteria | Agents working | Decided by |
|---|---|---|---|---|
| G0 | Lead | Lead Card with source URL, Buy Box fit score | A-01 | CEO |
| G1 | Screened | Fit score ≥ 60, quick zoning check not "Not permitted", owner identified from 登記 | A-01, A-03 (quick), A-04 (registry pull) | CEO, founder notified |
| G2 | Contacted | Approved first-touch letter or broker inquiry sent | A-02 | Founder approves each send |
| G3 | Engaged | Owner or broker has replied with interest; call or meeting booked | A-02 | CEO |
| G4 | Feasibility | Zoning Report + DD Report + Underwriting pack + 2 massing options, all reviewed by A-10; CEO Gate Memo with go / no-go | A-03, A-04, A-05, A-06, A-10 | Founder |
| G5 | Offer / LOI | Max bid approved; 買付証明書 or LOI signed by founder; 行政書士 / lawyer sign-off on zoning and title | A-05, A-08 (financing view) | Founder + professionals |
| G6 | Acquired | Settlement done by 司法書士; foreign-exchange and land-use filings submitted | A-03 (filings checklist), A-08 | Founder |
| G7 | Design | Architect contracted; design accepted; permit set ready for 建築確認 | A-06, A-07, A-05 (re-underwrite) | Founder + 一級建築士 |
| G8 | Build | GC awarded; construction to completion inspection (完了検査) | A-07, A-08 (lender draws) | Founder |
| G9 | Sell / operate | Units sold via licensed 宅建士, or handed to operator with 旅館業 licence | A-09, A-08 (investor reporting) | Founder |
1.3 Approval levels what an agent may do on its own
| Level | Meaning | Examples |
|---|---|---|
| L0 Autonomous | Agent acts, logs it | Web research, reading registries already paid for, running models, writing internal drafts, updating Deal Record fields it owns |
| L1 Notify | Agent acts, founder sees it in the Daily Brief | Advancing a deal G0→G1, spending within the task budget (e.g. ¥3,000 of registry pulls), re-prioritising the week |
| L2 Approve first | Agent prepares; founder approves in the queue; then the system executes | Any message to an outside party (owner, broker, 役所, GC, investor), spend above budget, sharing documents externally |
| L3 Human only | Agent may prepare material; a human performs the act | Offers and price statements, signing anything, paying or moving money, permit submissions, legal opinions, contract awards, investor solicitation |
1.4 Data contracts the two objects everything passes through
// Task Brief: CEO → worker
{
"task_id": "T-2026-1121-014",
"deal_id": "D-MYK-0042",
"agent": "A-03",
"objective": "Can a 10-key lodge be built and
licensed on this parcel?",
"inputs": ["deal://D-MYK-0042/lead_card",
"doc://D-MYK-0042/touki.pdf"],
"constraints": ["cite every finding",
"JP sources first"],
"budget": { "tokens": 400000, "jpy": 2000 },
"approval_level": "L0",
"due": "2026-11-24T18:00+09:00",
"done_when": "card:A-03#done",
"review": "A-10"
}
// Deal Record (abridged)
{
"deal_id": "D-MYK-0042",
"stage": "G3",
"area": "Myoko / Akakura",
"address": "新潟県妙高市赤倉 …",
"chiban": ["…番", "…番"],
"site_m2": 812,
"asking_jpy": 68000000,
"owner": { "ref": "crm://C-0193" }, // PII stays in CRM
"fit_score": 78,
"reports": { "zoning": "v2", "dd": "v1",
"uw": "v3", "massing": null },
"next_action": { "agent": "A-04",
"what": "boundary status",
"due": "2026-11-26" },
"risks": ["土砂災害警戒区域 edge", "no 境界確定"],
"log": "audit://D-MYK-0042"
}
Every worker returns a Result Envelope: {task_id, status: done | partial | blocked, deliverable_uri, done_when_checks: [{check, pass, evidence}], open_questions, needs, spend}. The CEO reads the checks, not just the prose.
1.5 Recommended tech stack
| Layer | Choice | Why |
|---|---|---|
| Agent runtime | Claude Managed Agents (beta) with multi-agent enabled; CEO as lead, workers as sub-agents referenced by ID | Anthropic hosts the loop and a sandbox per session, versioned agent configs, scheduled runs for the weekly sourcing sweep. Self-hosted alternative: Claude Agent SDK. |
| Models | CEO, Regulatory, Underwriting, Compliance: claude-opus-5-5. Other workers: claude-sonnet-5-5. Bulk listing extraction: claude-haiku-5-5 | Judgment-heavy roles get the strongest model; high-volume reading uses the cheaper ones. Measure before downgrading any role. |
| Deal Records / CRM | Notion or Airtable database (start), Postgres later | Founder can read and edit directly; agents use it through MCP. |
| Documents | Google Drive, one folder per deal ID | Shared with professionals; versioned. |
| Messaging | Gmail (draft-only scope for agents), Slack or LINE for the Daily Brief | Agents can draft but never send; send happens on approval. |
| Japan data sources | 国交省 不動産情報ライブラリ API, 登記情報提供サービス, 地理院地図, 重ねるハザードマップ, J-SHIS, municipal 例規集 and 都市計画 maps, BIT 競売, 空き家バンク | Primary public sources, citable in reports. |
| Observability | Audit log + per-deal spend ledger; Console session viewer | Founder can see what each agent did and what it cost. |
Product requirements
Problem: a ski-resort developer needs the output of a 6–10 person team (acquisitions, analyst, permitting coordinator, project manager, IR, bilingual assistant) before revenue can support one. Most of that work is research, Japanese paperwork, modelling and drafting, which agents can do; the rest is judgment and licensed acts, which stay human.
2.1 Users
2.2 Goals & success metrics targets to validate in Phase 1
| Goal | Metric | Baseline (manual) | Target |
|---|---|---|---|
| See more of the market | Leads screened per week | ~10 | 150+ |
| Faster no-gos | Lead → G4 feasibility pack | 3–4 weeks | ≤ 5 business days |
| Founder time on decisions only | Founder hours per deal reaching G4 | 25–40 h | ≤ 4 h |
| Trustworthy research | Regulatory findings with a primary-source citation | n/a | 100% |
| Trustworthy research | Findings overturned by 行政書士 / architect review | n/a | < 5% |
| Owner engagement | Reply rate on first-touch letters | unknown | ≥ 8% |
| Cost control | Model + data spend per G4 pack | n/a | ≤ ¥20,000 |
| Safety | Unapproved external sends or spends | n/a | 0 |
2.3 Non-goals
- Replacing licensed professionals or producing permit-ready drawings or legal opinions.
- Autonomous negotiation, offers, payments or signatures.
- Public-facing chat with buyers without a human in the loop.
- Property management and hotel operations (later phase, separate spec).
2.4 Functional requirements
| ID | Requirement | Priority |
|---|---|---|
| FR-01 | Founder can give goals in plain English or Japanese; the CEO turns them into Task Briefs and confirms its plan back in one message. | P0 |
| FR-02 | Daily Brief by 08:00 JST: decisions needed (with recommendation), pipeline moves, blockers, spend vs budget. | P0 |
| FR-03 | Weekly scheduled sourcing sweep across all sources for every target area, deduplicated against existing Deal Records. | P0 |
| FR-04 | Every regulatory and DD finding carries a source (URL or document + page/article) and retrieval date, or is marked "Unverified". | P0 |
| FR-05 | Approval queue: each item shows what will happen, to whom, the full text (JP + EN), cost, and Approve / Edit / Reject. | P0 |
| FR-06 | G4 Gate Memo bundles zoning, DD, underwriting and massing into one go / no-go page with links. | P0 |
| FR-07 | All owner-facing text is written in natural business Japanese (敬語) with an English translation for the founder. | P0 |
| FR-08 | Underwriting model is a real spreadsheet the founder can open and change, not numbers in prose. | P1 |
| FR-09 | Massing options rendered as diagrams with area tables; optional 3D site model. | P1 |
| FR-10 | Permit and construction tracker with critical path against the winter shutdown. | P2 |
| FR-11 | Investor materials trace every figure to an underwriting version ID. | P2 |
| FR-12 | Sales kit in EN / JP / 繁體中文, released only after 建築確認 is issued. | P3 |
2.5 Non-functional requirements
Every tool call, draft, spend and decision logged against a deal ID; replayable.
Owner names and addresses from registries live only in the CRM, used only for this acquisition purpose, never in prompts to outside services beyond what the task needs.
Per-task token and ¥ budgets; per-deal monthly cap; CEO halts and asks when 80% is reached.
Regulation KB entries older than 90 days are re-verified before use in a G4 pack.
Japanese sources are read in Japanese; reports are in English with original JP terms kept beside the translation.
Agents get draft-only email scopes and read-only finance access; secrets in a vault, never in prompts.
2.6 Rollout
| Phase | Weeks | Agents switched on | Exit test |
|---|---|---|---|
| P1 Desk research | 1–6 | A-00, A-01, A-03, A-04, A-05, A-10 | 3 real parcels taken to a G4 pack; 行政書士 overturns < 5% of zoning findings; founder ≤ 4 h each |
| P2 Contact & capital | 7–12 | + A-02, A-08 | 50 approved letters sent; zero unapproved sends; investor teaser for one deal |
| P3 Design & build | 13–24 | + A-06, A-07 | Architect accepts agent-prepared brief; permit tracker live on an acquired site |
| P4 Exit | 25+ | + A-09 | Sales kit approved by 宅建士 partner; leads triaged within 24 h |
2.7 Risks & mitigations
| Risk | Mitigation |
|---|---|
| Wrong zoning conclusion leads to a bad acquisition | Citation required per row; A-10 review; 行政書士 sign-off is a G5 exit criterion; 事前相談 with the town office before offer. |
| Outreach perceived as spam or intrusive | Postal letter or broker first; no marketing email without consent (特定電子メール法); founder approves every send; max 3 touches. |
| Agent drifts into licensed activity (brokerage, legal advice) | Hard rules in each card; no agent acts as intermediary for third parties; licensed partner handles contracts and 重要事項説明. |
| Advertising pre-construction units too early | A-09 blocked until 建築確認 is issued (宅建業法 advertising restriction). |
| Investor materials trigger securities rules | A-08 drafts only; counsel reviews any solicitation structure (金融商品取引法). |
| Stale data (ordinances, prices) | KB freshness rule; every report shows retrieval dates. |
| Runaway cost | Task budgets, per-deal caps, weekly spend line in the Daily Brief. |
2.8 Open questions for the founder
- Buy Box: target areas, land size, price band, and build-to-sell vs build-to-hold mix?
- Which entity buys (Japanese KK / GK vs foreign entity)? This changes 外為法 reporting and financing.
- Which professionals are already retained, and who receives agent packs?
- Deal Record home: Notion, Airtable or something you already use?
- Monthly budget ceiling for model + data spend?
Agent spec cards
Every card has the same six required fields: role, objective, inputs, tools, output format, and done when. Guardrails and hand-offs sit underneath. "Copy" puts the card on your clipboard as Markdown, ready to paste into an agent's system prompt.
| ID | Agent | Model | Default level | Phase |
|---|