Ourware

Learn

A free guide to how the Ourware family fits together — what each sister is for, and what it is not. Honesty badges stay visible on every page.

Learn path — Coming soonBrowse sisters

Stack overview

How the sisters relate — control surface, vault, documents, place, provenance, edge, and the build method.

Reading rule

Scooling is where you stand. Knowtation is what you stand on. StoreFree is what you keep. Born Free is where you gather. MuseHub is how it remembers who changed what. theBRAIN is how it reaches into a room — later. Overseer Kit is how we build it honestly.

That is the model, not a readiness shortcut. Pair this picture with the honesty labels in HONESTY-LABELS.md.

What problem this solves

  • DomainLife
    The problemYour memory is scattered across chat apps that own it, and the documents that matter are in an inbox.
    What the stack doesA vault you keep, documents that outlast the app, and a place to gather.
  • DomainWork
    The problemAI writes confidently into the wrong place; nobody can say who changed what.
    What the stack doesAgents propose and humans approve; typed history; a method that cannot fake DONE.
  • DomainPlay
    The problemCommunity happens in feeds that monetise attention and vanish.
    What the stack doesReal places, membership, credits, and lasting documents.
  • DomainResearch / field
    The problemFindings live on one person's laptop; provenance dies with the grant.
    What the stack doesVault, provenance, and collection at the edge.
  • DomainBusiness
    The problemEvery tool is rented; leaving means losing.
    What the stack doesPortable vaults, exportable files, and owned keys.

Continue with the collision glossary before using these nouns when talking about the products.

Sisters

Each card keeps honesty visible — what it is good for today, and what it is not yet for.

Glossary

This glossary only adds cross-product distinctions. Prefer each product’s own help for in-product terms. **Name the product before the noun:** say “Knowtation review,” “Scooling Review,” or “Overseer build review,” never an unqualified “review.”

Core collisions

  • WordReview
    Product-specific meaningsKnowtation proposal decision; Scooling Review/Decide; MuseHub proposal review; Overseer plan/build review
    Other meaning or boundaryFour different decisions with different authority
  • WordVault / Library / Docs-data
    Product-specific meaningsKnowtation vault; MuseHub view of a Knowtation-domain repository; Scooling Docs/data venue and Library grouping
    Other meaning or boundaryDo not call every store a vault or every Scooling document surface a library
  • WordProposal
    Product-specific meaningsKnowtation proposed write; MuseHub merge proposal; Scooling proposal receipt
    Other meaning or boundaryA Scooling receipt does not prove that a change was applied
  • WordHub
    Product-specific meaningsKnowtation Hub; MuseHub product; `muse hub` CLI namespace
    Other meaning or boundaryThe same suffix does not imply one application
  • WordAgent / helper
    Product-specific meaningsMuse/MuseHub identity and key slot; Scooling delegated helper; Knowtation scoped credential; Overseer automated build role
    Other meaning or boundary“Agent” alone does not identify scope or authority
  • WordBranch / history / version
    Product-specific meaningsGit branch/history; Muse intent-bearing branch, commit/symbol history, and schema/package/release versions; Knowtation History
    Other meaning or boundaryName both product and versioned object
  • WordLive / Preview / Pending / Operator
    Product-specific meaningsOurware sister readiness; Scooling surface readiness chips; human operator role
    Other meaning or boundaryA surface chip or source branch does not prove deployment
  • WordSpace / Guide / Guardian
    Product-specific meaningsScooling space and roles; Ourware Guide role; Born Free place and governance proxy role
    Other meaning or boundaryState whether the “space” is a team context or a physical place
  • WordDocument / note / workflow / flow
    Product-specific meaningsStoreFree document and signing workflow; Knowtation note; Scooling Docs/data and Flow
    Other meaning or boundaryA file, Markdown note, and saved procedure are not interchangeable
  • WordKey / credit / custody / posterity
    Product-specific meaningsBorn Free access Keys and reservation credits; cryptographic keys; StoreFree secrets, custody, and transfer feature
    Other meaning or boundaryA product name does not establish legal status or recovery rights
  • WordDomain / symbol / attestation / claim
    Product-specific meaningsMuse plugin and history nouns; DNS/product domain
    Other meaning or boundaryDo not infer legal or payment meaning from technical records

Additional operating collisions

  • WordPath
    Means in one placeScooling learning/work route
    Means elsewhereFilesystem path
  • WordTraining
    Means in one placeOurware Learn / training materials
    Means elsewhereScooling personal model Training Lab
  • WordDelegation
    Means in one placeScooling permission for a helper to act
    Means elsewhereKnowtation agent credential scope
  • WordModel
    Means in one placeScooling personal model/Training Lab
    Means elsewhereOverseer build-role label or an LLM
  • WordFlow
    Means in one placeScooling saved procedure
    Means elsewhereGeneric workflow
  • WordAdapter mode
    Means in one placeScooling capability posture
    Means elsewhereNot proof that runtime wires or deployed evidence exist
  • WordCommons
    Means in one placeOurware website platform name
    Means elsewhereNot a Born Free in-app noun
  • WordFreeze
    Means in one placeOverseer locked plan/spec before build
    Means elsewhereCraft instruction to lock one clear outcome

For product boundaries, continue to StoreFree vs Knowtation. For readiness, use Honesty labels.

Honesty labels

These six labels are the only readiness words we use publicly. Do not invent stronger claims.

  • LabelLive / beta Hub
    Visitor-facing explainerYou can use it today. Some Hub surfaces are still maturing — we say beta when a path is real but not finished.
  • LabelStaging
    Visitor-facing explainerA working preview environment. Explore freely; treat it as pre-production, not a final live cut.
  • LabelSoft-use / evolving
    Visitor-facing explainerYou can try it now while we keep improving it. Soft-use means real people can learn with it; evolving means features and polish still move — readiness stays labeled so you are never sold theater.
  • LabelVision / coming soon
    Visitor-facing explainerThe story and site are public so you can see the direction. Full product availability is still ahead — we will not pretend hardware or ops are shipping before they are.
  • LabelLive product
    Visitor-facing explainerA live product you can join or use today. Claims stay limited to what that project has actually shipped.
  • LabelBuilder-facing
    Visitor-facing explainerBuilt for makers and operators first. Useful now for AI-assisted work discipline; not a consumer app store listing.

An honesty label answers readiness, not adoption, legal effect, retention, or deployment equivalence. A preview surface does not prove a path is finished for everyone.

See the Learn hub for how labels appear on each sister.

StoreFree boundaries

**Knowtation is what you think with. StoreFree is what you keep.**

StoreFree ↔ Knowtation

  • BoundaryUnit
    StoreFreeDocument/file, media, or agreement
    KnowtationMarkdown note and its metadata
  • BoundaryPrimary job
    StoreFreeCustody, controlled sharing, signing record, optional long-term persistence, posterity
    KnowtationThinking, memory, retrieval, human-reviewed agent context
  • BoundarySystem of record
    StoreFreeEncrypted object plus workflow state; optional DocNFT/Arweave layer
    KnowtationUser-owned vault directory
  • BoundaryAgent relationship
    StoreFreeConsumer workflows may use it; agents are not its organizing unit
    KnowtationPropose/approve, CLI, MCP, and memory are central
  • BoundaryLoss/retention boundary
    StoreFreeSecret loss may be unrecoverable; non-DocNFT retention follows product/subscription rules
    KnowtationFiles remain ordinary readable Markdown; separate backup/encryption remains the owner's job
  • BoundaryIntegration truth
    StoreFreeSame Ourware family; do not imply automatic transfer between products
    KnowtationBorn Free ingestion into Knowtation stays off by default; do not assume they are linked

Born Free ↔ StoreFree

  • BoundaryPrimary job
    Born FreeMembership and access to places: Keys, credits, reservations, governance
    StoreFreeDocument custody, sharing, signing records, optional DocNFT, posterity
  • BoundaryMembership
    Born FreeCore to Born Free participation
    StoreFreeStandalone use exists; membership is not the product definition
  • BoundaryChain role
    Born FreeAvalanche membership/access assets plus IC-backed account paths
    StoreFreeIC document/workflow state; Avalanche only for optional DocNFT paths
  • BoundaryMoney shape
    Born FreeAccess and credit mechanics
    StoreFreeSubscription and optional document/workflow purchases; see current public product pricing — amounts are not listed here
  • BoundaryShared substrate
    Born FreeShared identity/session in the same product family
    StoreFreeSame app family, but not a Born Free feature bucket

This guide keeps Born Free and StoreFree distinct.

Use product-qualified nouns from the collision glossary, then continue to m03 — StoreFree or m02 — Knowtation.

Certificate of completion

Coming soon. The free Learn reading pages are available now. The quiz path and certificate of completion are not open to the public yet — more substance is still being written.

Earn a certificate — Coming soon