Real-estate investment intelligence and institutional RWA operating infrastructure — built as one programme, on one architecture, delivered in six months.
Hector and Kilo are a single pipeline built by one team. Hector proves an asset is worth owning; Kilo makes it rated, structured, and tokenisation-ready. Hector's evidence ledger is, literally, Kilo's admission gate.
The asset-management firm and originating deal pipeline — V5 / V10 / V20 funds. The owner of the assets that flow through the stack.
Originator · Balance sheet · BrandReal-estate investment intelligence & underwriting. Ingests a data room, structures and verifies it, scores risk and value, models repositioning and sensitivity, and answers questions against the evidence — every output traced to a source.
Ingest → Score → Reposition → Optimise → AskInstitutional RWA operating infrastructure. Takes a Hector-vetted asset and makes it rated, priced, structured, and tokenisation-ready — under Model B, where Valad remains the legal issuer and Kilo runs the engine beneath it. Smart contracts are retained by Valad.
Rate → Price → Structure → Subscribe → ReconcileEight engines, none deferred. The evidence ledger and data models are built first — the traceability schema the entire scope depends on. Extraction is proved on Valad's real documents in week three before any further commitment.
Every number Hector produces traces back to a source tier, with confidence and date. Missing data falls back gracefully to a lower tier — clearly labelled. This is a schema design, not a UI feature.
Rent rolls, leases, ASTs, EPCs, surveys, title, valuations. The asset-specific source of truth.
Licensed datasets — transactions, yields, rents, vacancy, planning, cost, climate. Benchmarking and calibration.
Government, statistical, agent research, news. Corroborating — used to triangulate assumptions.
The institutional off-chain layer that takes Hector-vetted assets and makes them rated, priced, structured, and tokenisation-ready. Model B: Valad is the legal issuer; Kilo is the engine beneath it. Smart-contract development, deployment, and audit are retained by Valad — that boundary is what makes the MVP shippable on this timeline.
Valad = legal issuer. Kilo = infrastructure operator. Kilo-as-issuer & retail are post-MVP.
DD gate consumes Hector's evidence ledger directly. Built by the same team — zero integration seam.
Smart-contract development, deployment, and security audit are retained and operated by Valad. Not in this scope.
Every partner integration behind a swappable adapter. Manual mode at MVP; live is configuration, not a code change.
Mostly third-party integrations surfaced through one controlled workflow. At MVP each is live, sandboxed, or a controlled manual workflow — behind a swappable adapter. Flipping manual to live is configuration.
The single most important flow in the system. A Hector asset that clears the eligibility gate becomes a Kilo operating pipeline — passed by reference, not re-keyed. The same team builds both sides; this is internal code, not a vendor integration.
Data room ingested, extracted, evidence-traced.
→Investment eligible — passes to Kilo.
→DD + evidence become Kilo's gate. No re-ingestion.
→Rated, priced, token-config packaged for Valad's layer.
Both products are built on a single core-evidence ledger. Kilo doesn't re-collect due diligence — it references Hector's score and evidence trail directly. Get this primitive right and traceability is inherited by both products for free.
Kilo.AssetSubmission → hectorAssetId · DueDiligence(E1) = HectorScore + ExtractedField[]
A single programme, one price. The shared team, shared architecture, and shared design system across Hector and Kilo are already reflected — you are not paying twice for foundational work.
A single TypeScript monorepo. The shared spine — auth, KYC, RBAC, audit, and the evidence ledger — is built once on Hector before Kilo depends on it.
# pnpm + Turborepo workspace packages/ core-evidence # Tier1/2/3 + confidence + source core-auth # org · RBAC · SSO core-kyc # 4-step KYC/AML · queue core-audit # append-only log (both write) core-db # Postgres schema + migrations ui # the dark Valad design system apps/ hector-web # Next.js · front-door + dashboards hector-api # ingestion · scoring · GPT kilo-web # issuer + investor dashboards kilo-api # institutional operating lifecycle engine-workers # Temporal · durable pipelines
Per-doc JSON schemas; Claude returns validated rows with confidence + Files-API citations stored as provenance. No number without its source.
High/Med/Low extraction review + missing-data prompts. The trust mechanism — and the liability shield.
Every integration is an interface — Particula, Chronicle, Morpho, Sky. Manual mode ships at MVP; live is configuration, not a code change.
Hector is the front door, the intelligence MVP, and the producer of Kilo's E1 input. Kilo mobilises at week 8 on the shared data model, design system, and team core. Both complete by month 6.
Tokenisation — the smart contracts that mint, hold, restrict and burn tokens, their deployment, and their security audit — is retained and operated by Valad. Kilo produces the configuration package and ingests on-chain events back for reconciliation. No contract build; no audit cycle on our side.
Rent rolls and leases come in every format. Mitigated by the per-field accuracy proof-of-concept on Valad's real documents in week 3 — SLAs agreed before any further commitment. The harness stays in CI as a permanent regression test.
Kilo's reconciliation requires Valad's tokenisation system to expose a defined interface or event stream. The integration contract is defined and agreed in weeks 7–10; a manual reconciliation path covers the period before Valad's live interface is ready.
KYC, jurisdiction whitelisting, and Reg S / MiCA / FCA controls need counsel — client-provided from week 1. Partners may be sandboxed/manual at MVP; the adapter pattern absorbs that without blocking the critical path.
Hector produces evidence and analytics — not RICS sign-off. That boundary is held in the data model, the UI, and the Report Centre output format. Formal valuation sign-off remains with Valad's appointed adviser.