A purchased build remains usable.
A future release cannot reach backward and disable the House already owned.
Systead private pre-alpha
No public or supported tester build exists yet. The intended future product is being shaped as a finite licence—not a monthly subscription, not a consultancy package, and not a cloud account that becomes useless when payments stop.
What “controlled” means
Fast does not mean frantic. The private pre-alpha earns trust by making intent, affected records, risk, approval, verification, and recovery visible in one place.
A future release cannot reach backward and disable the House already owned.
Another version must earn another payment through clear new value. Staying on the owned build remains a valid choice.
Readable export, documented records, and recovery must work without requiring a support contract or continued payment.
Enabled Programs, supported platforms, migrations, safety limits, and incomplete areas are stated before any purchase.
Documentation, fixes, and a bounded issue channel may exist. Personal workflow consulting is not required to obtain value.
The private proving sequence
The pre-alpha advances only when the prior run proves its promises under synthetic data and a real private proving House.
Return, understand, capture, review, decide, export, and reset across Publishing, Shared Home, and Property.
Extract the first clean reusable Program from the private AuthorMachine and Stokknes proving line.
Prove that the same House foundations support co-rent, household, renter, and family profiles.
Prove the owner-side sibling without collapsing resident privacy and property authority into one model.
Intended local delivery
The current run is a browser prototype. The target is an ordinary local desktop application whose data remains on the operator's machine, with an optional Android companion paired over the same Wi-Fi.
Programs, local database, files, review, export, backup, recovery, and device permissions remain under one local authority.
The phone receives only selected Programs and actions. Pairing is explicit, revocable, encrypted, and off by default.
Now: local browser pre-alpha. Next: durable local core and Windows shell. Then: narrow QR-paired phone workflow. No public installer or companion exists yet.
What pre-alpha is for
The founding price will be set only after First House proves the core loop and Folio has a supportable installation, migration, recovery, and exit path on another machine.
A first closed outside candidate before the end of 2026 is an aspiration, not a release promise. Readiness gates win over the calendar.
Inspect the Program scopePlain answers
No. The current system is a private pre-alpha under real internal use. There is no public tester package or supported installer yet.
The intended commercial direction is a one-time product licence. Hosted or synchronization services, if they ever exist, would need their own separate justification.
No. A bounded import path and clear documentation are product requirements. Personal implementation services are not the route being pursued.
No. AuthorMachine remains the internal name for the private publishing proving line. Folio is the pre-alpha codename; Publishing House is the descriptive working label. None is a cleared release name.
The Systead application and a useful local House foundation: capture, generic records, search, decisions, review, backup, recovery, and readable exit. Specialist Programs provide the paid domain depth. Final public licence terms remain open.
No. It is the second active proving direction and exists in the private pre-alpha 00 synthetic House. Its purpose is to prove profiles, shared responsibility, tenancy evidence, and clean exit.
Yes. Hearth is resident-side household continuity; Keystone is owner-side property continuity. They may exchange an explicitly shared maintenance or handover record, but not silently share private House data or authority.
They must be able to. A House without understandable export, recovery, and removal behaviour is not ready to be sold as Systead.