Useful before large
Would this still help five people who already know why they are here? Five is a design test, not a universal promise.
Product direction
Building the smallest real network.
The first version is bounded around one useful journey: an organizer shares something meaningful, people join and participate, a real need appears, and the group can carry that need toward a trusted capability.
First-version outcomes
Enough network, spaces, and trust to prove one complete loop.
This is the product destination we are aiming to create first—not a catalogue of speculative later features or invented dates.
- Network membership without requiring Aitta ownership
- Verified Aitta registration, discovery, invitations, Follow, Unfollow, and Your network
- Public typed events and recursive spaces with explicit access and authority
- Consent-based direct conversation spaces
- Reporting, blocking, credential revocation, and recovery foundations across network participation
- An accountable App Idea process
- A reviewed trusted-app development and release loop
Product doctrine
Five principles keep growth useful and understandable.
Grows in context
Add the useful interaction where the need appeared, with its people and history attached.
Participation without ownership
Members can follow, join, respond, message, and use apps without deploying an Aitta.
Composable, not chaotic
Keep current context, ancestry, access, navigation, depth, fallback, ownership, and authority understandable.
Trust by design
Independent authority and local software trust explain why remote events cannot make an Aitta run arbitrary code.
Trusted release loop
Needs become reviewed capability—not arbitrary live code.
- 1Need
- 2App Idea
- 3Participation
- 4Specification
- 5Agent implementation
- 6Tests and review
- 7Approved release
- 8Adoption
- 9Improvement
Agents may summarize discussion, draft contracts, implement on a branch, add tests, run checks, and prepare release notes. A human approves every platform release.
Consent-based conversation
A private conversation begins only after the request is accepted.
A member first sends a message request to an Aitta. An owner or authorized participant can accept, decline, block, or report it. Only acceptance opens the private conversation.
Rate limits, safe notification previews, explicit retention, unread state, blocking, and reporting protect the boundary. Once accepted, the conversation can contain other trusted apps.
What the first demonstration must prove
It started as a message—and became useful.
- An organizer shares something.
- People discuss it.
- A need emerges.
- An App Idea forms around it.
- Agents help implement a reviewed capability.
- The release appears in the same context.
- The group uses and improves it.
How we will hold ourselves accountable
Weekly Participating Spaces
A participating space requires at least two distinct people or Aittas and a meaningful child event or state transition during the week. A raw view or isolated root message does not qualify. Early learning focuses on return, participation, time to first child event, and App Ideas reaching decisions or releases—not empty accounts, posts, followers, or app count.
A useful acquisition loop
One real group can make the next one curious.
- 1Organizer shares
- 2Invites existing people
- 3People participate
- 4A new need appears
- 5Group shapes an App Idea
- 6Trusted capability releases
- 7The Aitta becomes more useful
- 8Another organizer wants one
This loop begins with direct links, invitations, and useful public Aitta pages—not broad promotion into an empty global feed.
Open development