OpenTwin is the open standard that lets any property share its data — maintenance records, financial history, IoT devices, residents — with any authorised application, in one canonical shape.
{ "opentwinVersion": "0.3.0", "home": { "nestCode": "hin:v1:IN:7e3cf2a148b9d0c4", "propertyType": "apartment", "builtUpAreaSqft": 1240, "maintenanceScore": 100, "riskScore": 72 }, "assets": […4], "devices": […7], "documents": […12], "people": […3 residents], "gateLog": […48 events], "governance": { "activePoll": true }, "parking": […2 bays] }
Any compliant platform produces this schema. Any authorised consumer reads it. The owner controls every access decision via EdDSA-signed consent tokens.
A consent token names who gets what data, for which purpose, for how long. EdDSA-signed. 24-hour default expiry. Revocation in 60 seconds. No implicit inheritance — owner consent does not extend to tenant PII.
NestBrain is a proprietary ML model that scores property health from 0–100 across six measurable factors. Updated in real time as the property's data changes — not recalculated annually from a questionnaire.
read:twin scope.OpenTwin RFC-0023 standardises the data schema for housing society governance: resident polls, board elections, AGM proceedings, bylaw amendments, and quorum tracking. Results are anchored to the community twin's HMAC-chained lifecycle log.
governance.* scope. A regulator querying maintenance compliance can also verify that the maintenance budget was voted in by a quorum — end-to-end accountability.// RFC-0023 Governance schema fragment interface SocietyPoll { pollId: string; // UUID question: string; pollType: 'resolution' | 'election' | 'agm_motion' | 'bylaw_amendment'; quorumPct: number; // Required % status: 'open' | 'closed' | 'passed' | 'failed'; votes: { yes: number, no: number, abstain: number }; lifecycleRef: string; // HMAC-chain anchor }
RFC-0025 defines the canonical gate pass schema — pre-authorised QR codes, real-time approval flows, delivery authorisation, and a 20-minute AES-256-GCM offline cache. Any access control hardware vendor can implement it once.
// RFC-0025 Gate pass schema fragment interface GatePass { passId: string; passType: 'resident_auth' | 'pre_approved' | 'delivery_one_time' | 'service_visit'; homeId: string; // NestCode / HIN validFrom: ISODate; validUntil: ISODate | null; qrPayload: string; // AES-GCM, 20min TTL consentScope: 'opentwin.gate.pass.read'; }
Apache 2.0. Public GitHub. New RFCs via pull request. RFCs 0023–0028 are newly drafted, grounded in live SeekYourNest features.
Maintenance compliance, valuation history, ownership chain — one API call. The same code works across every compliant platform.
NestBrain score + IoT device health + maintenance records, updated in real time. Pilot: very_low band → −15% premium.
RFC-0011 MCP tools. One implementation works on every compliant platform — Claude, GPT-4o, Gemini all use the same schema.
Implement OpenTwin once. Your product reads every compliant platform's data. Level 1 cert is free and self-attested.
Add NestCode as a secondary column. Print it on title deeds. Three adoption tiers from a SQL ALTER TABLE to W3C Verified Issuer.
RFC-0025 defines the canonical visitor auth schema. Build hardware once — it works in any OpenTwin-compliant society management system.
28 RFCs in draft. Conformance suite live. Every adopter shapes what v1.0 looks like. Apache 2.0.