A purchased build remains usable.
A future release cannot reach backward and disable the House already owned.
Systead private pre-alpha
Not released.
Building carefully.
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.
Commercial directionOne-time licence
House foundationUseful free base
Primary candidateFolio · Publishing Program
Resident-side proofHearth · Shared Home
Owner-side proofKeystone · Property Steward
Current statePrivate pre-alpha 00
What “controlled” means
The operator sees the change before Systead makes it.
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.
Future major versions are optional purchases.
Another version must earn another payment through clear new value. Staying on the owned build remains a valid choice.
Exit is included, not negotiated.
Readable export, documented records, and recovery must work without requiring a support contract or continued payment.
The offer is honest about scope.
Enabled Programs, supported platforms, migrations, safety limits, and incomplete areas are stated before any purchase.
Support does not become the product.
Documentation, fixes, and a bounded issue channel may exist. Personal workflow consulting is not required to obtain value.
The private proving sequence
One loop. Three Programs. Increasing consequence.
The pre-alpha advances only when the prior run proves its promises under synthetic data and a real private proving House.
Run 00 · First HouseInternal now
House Loop
Return, understand, capture, review, decide, export, and reset across Publishing, Shared Home, and Property.
- Local browser persistence
- Shared Core records
- Three focus Programs
- Readable House export
Run 01 · FolioNext
Publishing Program
Extract reusable publishing workflows from the broader private Stokknes House build, replacing private records with synthetic fixtures.
- Catalogue and project state
- Production and release
- Decisions and file standing
- Assisted import without consultancy dependency
Run 02 · HearthFollowing
Shared Home
Prove that the same House foundations support co-rent, household, renter, and family profiles.
- People and agreements
- Services and shared ledger
- Maintenance evidence
- Move and exit state
Run 03 · KeystoneThird focus
Property Steward
Prove the owner-side sibling without collapsing resident privacy and property authority into one model.
- Properties and tenancies
- Condition and inspections
- Maintenance and vendors
- Documents, costs, and handover
Intended local delivery
One Windows House.
A nearby phone companion.
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.
The House lives here.
Programs, local database, files, review, export, backup, recovery, and device permissions remain under one local authority.
- Installable `.exe` direction
- Useful without internet or cloud account
- Complete House control and exit
QR pairlocal Wi-Fi
Capture and consult nearby.
The phone receives only selected Programs and actions. Pairing is explicit, revocable, encrypted, and off by default.
- Photos, receipts, notes, and quick tasks
- Nearby household or property facts
- Installable web companion first; native later if earned
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
Prove ownership and continuity before scale.
- Local-first single House
- Publishing, Shared Home, and Property focus
- Synthetic and deliberately imported records
- Human review before consequence
- Complete readable export
- Explicit backup and recovery drills
- Autonomous external action
- Cloud collaboration
- Mobile parity
- Enterprise permissions
- Full accounting or legal authority
- Every private v10 feature
Nothing is for sale yet
The licence is decided before the price is invented.
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
Before anybody buys anything.
Can I download or use Systead now?
No. The current system is a private pre-alpha under real internal use. There is no public tester package or supported installer yet.
Is Systead becoming a subscription?
The intended commercial direction is a one-time product licence. Hosted or synchronization services, if they ever exist, would need their own separate justification.
Does the alpha require consultancy?
No. A bounded import path and clear documentation are product requirements. The separately planned website service delivers client websites; it is not a prerequisite for using Systead software.
Is AuthorMachine the release name?
No. AuthorMachine is a historical internal name for the wider private Stokknes House build. Folio is the current working name for the reusable Publishing Program extracted from its publishing workflows. Neither is an announced release name.
Is Stokknes House the Systead demo?
No. Stokknes House is the founder’s private operational environment. Pre-alpha 00 is a separate synthetic product prototype. The public interface studies illustrate the product direction; they do not expose private House records. Read the relationship.
Can I commission a website?
The website service is Systead’s current service focus. Prepare an estimate and brief, then agree a written scope, fixed price and delivery slot. No checkout or booking commitment is created here.
What is intended to be free?
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.
Is Shared Home already a released product?
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.
Is Property Steward separate from Shared Home?
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.
Can the operator leave?
They must be able to. A House without understandable export, recovery, and removal behaviour is not ready to be sold as Systead.