Gran Canaria: the system, exercised
Before ASTIN was offered to anyone, it was run against a real asset with a real independent counterparty. This page sets out precisely what that exercise covered, what it does not prove, and what remains for commercial deployment.
Operating context
Lars Astor acquired a residential property in Gran Canaria and, for a period, operated it in co-ownership with an independent minority investor. Both parties were individual investors, holding unequal positions. The property served as a seasonal remote-working base for delivery to clients in Luxembourg and Belgium, and was otherwise managed remotely through local subcontractors — legal and financial services, periodic renovation work, and medium-term lettings typically of up to six months.
That arrangement was not a pilot staged for a product. It was an actual cross-border co-ownership, with actual money, actual documents and an actual counterparty who had every reason to challenge anything that did not add up. A working ASTIN prototype was run against it — the real asset, the real holdings and the real exit — rather than against a scenario invented to flatter the software.
The challenge
Two owners with unequal holdings, one calendar with sharply unequal seasonal value, running costs to divide, a letting operation to reconcile, documentation spread across two jurisdictions, and — eventually — a minority exit that had to be prepared, agreed and executed under Spanish law.
Functions exercised
Each of the following was carried out against the real asset and the real counterparty.
- Asset onboardingThe property, its legal identification, operating budget and document set were modelled as a single record.
- Ownership structureA majority and an independent minority interest were represented, with the rights attaching to each.
- Co-investor onboardingThe second party was taken through documentation, share economics, usage rules and exit terms.
- Calendar allocationSeasonal value was priced and divided against the actual holdings.
- Cost and revenue attributionRunning costs and letting income were attributed across the holdings over the period of joint ownership.
- Transfer preparationThe minority exit was prepared to the point where both parties were ready to execute.
- Post-transfer stateThe resulting ownership position was recorded once the transfer completed.
Why the independent investor matters
A demonstration run by a founder against their own asset proves very little: there is no second opinion and no adverse interest. Here there was an unrelated minority holder with their own capital, their own view on the calendar, their own accountant and their own exit intentions. Every figure the system produced had to be acceptable to someone with a reason to dispute it — and the system was used with them, not merely shown to them.
The transfer of the minority interest to the majority holder was executed before a notary, as Spanish law requires. ASTIN neither performed nor replaced that act.
That boundary is the product’s design, not a shortfall in it. The system’s task is to orchestrate and record the process around a legally reserved act — the same relationship a mortgage platform has with a land registry. The case was carried to a ready state, the authorised party executed, and the resulting state was recorded.
Ownership was subsequently consolidated to a single holder.
What this establishes
- The workflow closes. Acquisition, co-ownership, use, operation, exit preparation and the recording of the result were all exercised — not just the attractive parts.
- The domain logic survived contact with a counterparty who did not build it and had every reason to challenge it.
- The external boundary is real, and was respected at the one point where the law requires it.
- The requirements come from operating a cross-border asset, not from a market study.
Operational maturity
Taken together, this is a system prototype demonstrated end to end in a real operating environment — the basis for our own assessment that ASTIN sits at approximately TRL 7. It is a statement about the prototype, not about commercial readiness: the next levels belong to production hardening and first deployment, and neither has happened.
What it does not demonstrate
Stated plainly, because a partner will find these anyway.
- It is not a commercial rollout, and there is no customer. The scope was one asset, one jurisdiction and one independent counterparty.
- It does not validate the Dubai transaction route. DLD and DET processes require their own local legal and operational validation before any deployment.
- It does not prove scale. Multi-asset operations, high owner counts and letting volume are ahead of the product, not behind it.
- It does not evidence a customer-acquisition channel. None is operating.
- It is not TRL 8 or 9. A prototype demonstrated in a real environment is not a qualified system, and we do not present it as one.
- The demonstration on this site is a synthetic reconstruction for evaluation. It is not the historical build and is not offered as evidence of the case.
What was actually running
The distinction that matters: this was a working ASTIN prototype exercised against a live arrangement, not a business model discussed around one.
Asset and ownership
The real property was onboarded and its ownership structure represented, including the unequal split between the two holders.
Co-investor onboarding
The minority investor was taken through the arrangement inside the system — documentation, share economics and the rules attaching to their position.
Calendar and economics
Seasonal usage rights were allocated against the holdings, and operating costs and letting revenue were attributed across them.
Administration
The co-ownership position was administered over the period the arrangement ran, not modelled once and abandoned.
Exit preparation
The minority exit was prepared and the interest transfer carried to a transaction-ready state.
Recording the result
After the external act completed, the resulting ownership state was recorded in the system.
Where this account comes from
This case is stated on the authority of the founder, who was the majority owner throughout. It is a historical operating case, not an audited one, and we describe it as such rather than dressing it up as independent verification.
The underlying property, co-ownership and notarial records are not published. They contain property-specific detail and information about a third party who has no reason to have their affairs on a company website.
The demonstration on this site is a separate, synthetic reconstruction of the same workflow, built for evaluation. It is not the historical build and contains no real party, document or amount from the case.
What remains for production deployment
- Local legal and regulatory validation of the transaction route in the target market
- Integration with the letting operator’s reporting for automated settlement ingestion
- Formal document retention, backup and access-control policy for production data
- Localisation of contract templates and buyer-facing documentation
- Operational hardening under multi-asset load
See it running
The demonstration environment carries a synthetic asset through the entire life cycle, in four operational roles, with persistence — reload and the state is still there.