Vision · roadmap architecture · nothing here is launched
The future Sigmastead fabric.
Where this is going, separated by horizon. A private vault and goal loop can become infrastructure for a user-controlled economy—but only in layers, each earned before the next.
“Fabric” means a shared permission and trust layer through which separate applications could request narrowly scoped access. It does not mean one application receives the whole vault.
Everything on this page is design direction recorded in the product record. Where a piece exists in synthetic development it says so; everything else is future architecture.
Describe the life you want to build.
The Vision Board is a named product capability, not a text form. The smallest useful version lets an adult create private vision areas, add an outcome, a motivation, a timeframe, an image or reference, and their own words; connect an area to one or more goals; choose which evidence categories may inform each goal; and see goal, evidence, observations, experiments, and Goal Momentum as one coherent story. Correct, archive, export, and delete all of it. Use it on a phone, with a keyboard, with a screen reader.
Health
Finish the spring race without running myself down.Time
Protect two quiet evenings a week.Learning
Read for enjoyment, not completion.Money
Know where the month goes before it goes.Experience
One trip with the family this year.Career
Present the architecture work I'm proud of.Sketch · synthetic · designed, not built · images and free text stay out of analysis packets by default
Permission layers, not launched products.
-
Nowsynthetic development
Private vault and goals. Chosen data, customer-controlled keys, the reviewed packet, cited guidance, voluntary action, Goal Momentum. Proving the loop coherent, useful, and honest with synthetic and non-sensitive data.
-
Nextinvited adult U.S. alpha
Selective sharing. Gated by independent vault, recovery, and hosted release review; the applicable operational-security baseline; legal review; device evidence; pricing; and support.
-
Verified peopleDesigned · active build / M5
Portable credentials present issuer-verifiable education, certification, achievement, and skill claims in interoperable formats—the minimum necessary claim rather than a whole history. A verified-person marketplace may help an invited individual find and book someone because of one exact evidence-linked credential or accomplishment—not a blanket “verified expert” label. Professional credentials come first; peer mentorship follows only after one real in-network transaction proves the mechanism. Payment execution is not yet built.
-
Laterresearch and terms
Controlled research licensing stays separate: a verified organization publishes a request; your device evaluates it locally; only if you choose to participate is a minimized manifest disclosed and an agreement, delivery, and settlement recorded. You license a bounded use—never yourself.
A separate terms-integrity capability may eventually let you publish exact licensing terms with dated, hashed, tamper-evident evidence. It is designed, not built. A hash can detect a change; it does not by itself prove publication time.
-
Only aftercontrols exist
Creator publishing, storefront, and community. Deliberately last, because a public surface creates obligations a private vault does not: moderation, appeals, copyright, impersonation, fraud, harassment, age assurance, transparency. It arrives only with identity, payments, safety, moderation, portability, legal, and dispute controls in place.
Roadmap architecture · not launched
A public post is never permission to use a private vault.
- Encrypted customer material
- Unavailable to other users
- Unreadable by Tech City
- Content for named people, groups, or subscribers under explicit terms
- An exact dataset or claim released to a verified buyer under a separate purpose, duration, compensation, onward-use, and deletion agreement
- Pseudonymous control records, never anonymous
- Material you deliberately make public
- Clear notice that copying and capture cannot be recalled
- Moderated under disclosed rules—never a back door into the vault
A follow, like, comment, or view is not consent to license unrelated vault data. Private vault data never silently becomes public, advertising, model-training, social, or marketplace data.
You keep most of the value you create.
Transparent fees
Storage and analysis allowances, payment-processing pass-through, and a disclosed share of transactions—shown before you accept anything. No exact prices are selected yet.
No privileged buyer
No organization, however large, receives private data without the same verified request, exact agreement, your approval, encrypted delivery, and payment controls.
Portable by design
Original content, relationships, agreements, and transaction history in documented formats that stay useful without Sigmastead.
Other people's data is theirs. A message, image, voice, health detail, or authored contribution from someone else cannot be licensed merely because it appears in your account.
A fabric other apps can join—on your terms.
Separately built applications may one day connect through a versioned developer gateway with purpose-specific scopes you select, explicit consent, revocation, rate limits, and audited contracts. A partner app is a separate application, never a trusted internal service: it gets no direct database, administrator, or whole-vault access.
Directional design · not implemented · does not expand the current alpha
What stopping can and cannot do.
Sigmastead can stop future platform access and delete service-held copies. It cannot erase material already downloaded, viewed, recorded, republished, or incorporated into completed research. Every sharing, licensing, and publishing flow says this before you act, not after.