Configured around the operator
Selected Rooms, Desks, records, Programs, permissions, connectors, and practical routines.
The House
One private place to return to.
A House is one operator’s configured Systead environment.
It can begin with a few calm surfaces and grow into serious continuity infrastructure without showing all of its machinery at once.
The lived product
The House is what the operator experiences. Core is what makes it trustworthy.
The architecture exists to support the House, not to force the operator to think like a systems engineer.
Change, attention, active work, waiting items, decisions, and review.
Broad domains such as Work, Knowledge, Household, Contacts, or Administration.
Focused operational surfaces within a Room.
Inspectable intelligence that can observe, explain, propose, stage, and verify.
Optional deep specialist applications using shared House foundations.
Human-readable export, machine-readable manifests, recovery, and migration.
Progressive disclosure
A calm front door. Serious depth behind it.
The private proving build is dense because it carries real accumulated complexity. The public product needs clearer layers.
Calm starting surface
What changed, what needs attention, quick capture, search, and active areas.
Working Rooms
Records, relationships, timelines, decisions, status, next actions, and relevant tools.
Machinery underneath
Provenance, canonical ownership, conflict resolution, audit, automation rules, recovery, and system health.
What belongs in a House
Only what earns a place.
A House should be selective. Not every user receives every Room, and not every record deserves permanent operational weight.
01Active work
Projects and responsibilities with consequences.
Current state, dependencies, decisions, evidence, next actions, and completion conditions.
02Durable knowledge
Information that must remain understandable later.
Sources, manuals, research, previous conclusions, standing, contradictions, and review dates.
03People and commitments
Relationships as context—not surveillance.
Relevant history, agreements, responsibilities, follow-up, boundaries, and consent-aware records.
04Practical reality
The obligations ordinary software treats as miscellaneous.
Assets, services, maintenance, household administration, documents, and recurring reviews.
05Specialist depth
Programs where a domain demands more than generic records.
Deep workflows operate inside the House while respecting Core authority and portability.
The House should survive
Not only the next sprint. The next interruption.
The system should make return, reconstruction, recovery, and exit first-class product experiences.
Survive weeks or months away.
Survive a failed device or damaged index.
Survive changing tools and AI providers.
Survive a Program being removed.
Survive Systead itself being replaced.
Remain legible to the operator.
The founder’s proving ground
Three names.
Clear responsibilities.
A House can hold several operations while keeping their identities, records and permissions distinct. Stokknes House is one private example of that broader idea.
Stokknes House
The founder’s command centre across publishing, freelance work, household responsibilities and developing Systead. Its private build has used the AuthorMachine and Stokknes OS names.
Its role covers the whole operation. A publishing workflow is one part of that House.
Private build · not a public downloadStokknes Publishing House
The author-led imprint behind the books, editions, rights and releases. Its public home is M. J. Stokknes’s author website.
Visit the publishing imprintSystead
The platform and Programs being developed for other operators, alongside a separately scoped website service. This website presents that work and its current readiness.
Explore Systead ProgramsPublishing Program ≠ publishing imprint. Folio is the working name for reusable publishing software. Stokknes Publishing House is an operation that can use it. Private House records remain private; public examples use synthetic data.