A Day at the Office¶
What does a normal day actually look like?¶
You have your Passport. You know the rules. You've read the thesis.
Now what?
This page walks you through a typical day as an active participant in Smartup Zero. One person, one day, every layer of the system — in the order you'll actually encounter them.
Read it once. Come out the other end knowing how everything connects — and how your daily work becomes part of the experiment's evidence.
Meet Asel¶
Asel is a contributor from Bishkek, Kyrgyzstan.
She holds a Work License, is a junior (Defender) on the Media team (3_5),
and has been in the system for three weeks.
She is not a founder. She is not a captain. She is exactly the kind of person Smartup Zero was built for — talented, values-driven, tired of watching from the sidelines.
This is her Tuesday.
8:00 — She Opens Element¶
Element is the front door to the entire SmartupOS workspace.
Not a website. Not an app. A federated, EU-sovereign, encrypted chat platform
running on the Smartup Zero homeserver at owners.smartup0.org.
Every room she can see is a layer of the organisation:
🌐 1_general_forum ← Public democracy. Anyone can read. Owners can vote.
🏢 2_workplace ← The coordination layer. Objectives, ledger, big picture.
🎨 3_5_media_team ← Her team. Where the actual work happens.
🤖 Engelbot DM ← Her direct line to the ledger.
She types her first command of the day:
!whoami
Engelbot replies with her identity card — alias, license type, team membership, current SK score, and role assignment. It takes two seconds. The ledger already knows who she is.
Layer 0 — Element / Matrix
Element sits below all the numbered layers — it is the interface through which every layer is accessed. Everything Asel does today happens through a Matrix room or an Engelbot command. Read more about Element →
8:15 — She Checks the General Forum¶
Before diving into work, Asel checks 1_general_forum.
This is the public democracy layer — the room where governance happens. Proposals are posted here. Votes are called here. The constitution lives here. Anyone in the world can read it. Only verified owners can vote.
This morning there is an open proposal:
"5_8_0 — Proposal to add a Science team captain stipend." Status: Open for comment. Lazy consensus closes in 31 hours.
Asel reads it. She agrees. She types nothing — silence is consent in lazy consensus. If she disagreed, she would reply with her objection and it would go to a full vote.
She checks her voting weight with !wallet. She has 67 SK.
Her voting weight is 1.07 — above the base 1.0 because she has been showing up consistently.
Layer 1 — The General Forum
1_general_forum is where Smartup Zero meets democracy.
Proposals, votes, constitutional amendments, and public transparency reports all live here.
Every owner has one vote — Campaign, Watch, Work, Group, and Founder alike.
SK adds weight (max 1.5 at 500 SK) but never overrides the one-person-one-vote principle.
Key concepts here: - Lazy consensus: 48h silence = consent - 50 SK minimum to propose a vote - Constitution amendments require explicit vote — never lazy consensus - All ledger data is mirrored here for public transparency
How this feeds the experiment
Asel's vote (and her choice to abstain) are recorded in master-events.csv.
This feeds directly into the Decision Participation Rate and Proposal Origin Diversity —
key metrics for Indicator 4 (Self‑Understanding) and Indicator 8 (Coordination).
8:30 — She Checks the Workplace¶
Asel opens 2_workplace. This is the coordination layer — the room that sees everything.
She types:
!show 5_0
Engelbot returns the global mission overview — all active objectives, their progress, which teams own them, and what percentage of tasks are complete.
She sees her team's objective — 5_6_5, a media objective to produce a series of
explainer videos about the SC/SK currency system — is at 40% progress.
Three tasks complete, two still open.
This is where SC lives. Every objective is budgeted in Smartup Credits. Every task draws from that budget. Every payout is traceable back to this room.
Layer 2 — The Workplace
2_workplace is the single source of truth for the entire experiment.
The Forgejo ledger that backs this room holds every CSV, every wiki page,
every SC transaction, every audit trail entry.
Asel can see:
- Active global and team objectives (5_X, 5_X_Y)
- SC treasury health
- Task completion rates across all teams
- The Book of Owners
She cannot edit anything here directly. Every mutation goes through Engelbot → Toolbox → ledger.
How this feeds the experiment
The !show 5_0 command is a read operation, but the data she retrieves —
objective progress, task completion rates — is generated by the system continuously.
The Plan Effectiveness metric (Indicator 7) and Objective Completion Rate (Indicator 8)
are calculated from this same underlying data.
8:45 — She Opens the Media Team Room¶
Asel moves to 3_5_media_team. This is her team's room — where coordination,
planning, and task handoffs happen in conversation.
The seven teams are:
| ID | Team | What they build |
|---|---|---|
3_1 |
Leadership | Strategy, governance, SmartupOS infrastructure |
3_2 |
Design | UX, visual identity, product design |
3_3 |
Developer | Technical architecture, Engelbot, Toolbox |
3_4 |
Business | Revenue model, licensing, financial flows |
3_5 |
Media | Storytelling, communications, community |
3_6 |
Science | Research, validation, methodology |
3_7 |
Operational | Coordination, onboarding, day-to-day ops |
Her captain — the elected coordinator of the Media team — has posted a message:
"6_5_5_2 is ready to claim. Senior Attacker needed. Who's taking it?"
Asel checks the task:
!show 6_5_5_2
Layer 3 — Teams
Teams are small, autonomous, and self-governing. Each team elects its own captain (requires 100 SK minimum to run). Captains coordinate — they do not command. They can be recalled by the team via a governance proposal.
The seven team captains together form the Leadership Team (3_1).
Major decisions require their alignment. Day-to-day decisions happen at team level.
How this feeds the experiment
The task assignment (when Sam claims it) creates a new entry in task-budgets.csv
and a cross‑team pairing if Sam and Asel are from different teams.
This feeds the Capability Diversity Index (Indicator 3) and
Cross‑Functional Collaboration Rate (Indicator 3).
9:00 — She Looks at Her Role¶
The task requires a Senior Attacker. Asel is a Junior Defender. She cannot claim this one — but she makes a note to apply for a senior role once her SK grows.
She checks the open roles:
!open_roles
Engelbot lists every role currently accepting applications across all seven teams. Each role has a defined SC earning potential, a time commitment, and a skills brief.
Roles in Smartup Zero follow the permission code pattern:
| Code | Seniority | Function |
|---|---|---|
4_1_X |
Captain | Team coordinator. Elected. Recallable. |
4_2_X |
Senior (Attacker) | Executes work. Primary SC earner (90%). |
4_3_X |
Junior (Defender) | Oversees quality. Secondary SC earner (10%). |
4_0_X |
Mission Leader | Coordinates objectives. Appointed by captains. |
She is 4_3_5 — Junior Defender on team 5.
Layer 4 — Roles
Roles gate which Engelbot commands you can run, which tasks you can claim, and which scripts execute on your behalf.
Roles are applied for, assessed, and can be updated as your contribution and SK grow. The system is designed for horizontal career development — you can move between teams and roles as your skills evolve.
How this feeds the experiment
The open roles list shows the current state of Role Coverage — a component of Indicator 4 (Self‑Understanding). When Asel applies for a senior role later, that application will be logged and will eventually shift the Authority Concentration Index as she gains more responsibility.
9:15 — She Checks Her Tasks¶
!my_tasks
Engelbot returns her current task list. She has one assigned task:
6_4_5_1— Write the SC/SK explainer script for video #2 Status: assigned · Budget: 50 SC · Attacker: sam · Defender: asel
She is the Defender on this task. Sam is the Attacker. The ADM triangle in action — Sam executes, Asel oversees.
Layer 5 — Objectives
Before tasks exist, objectives define the direction.
Global objectives (5_X) — organisation-wide missions.
Team objectives (5_X_Y) — specific deliverables owned by one team.
Every task (6_X_Y_Z) belongs to a team objective.
Progress rolls up automatically through the ledger.
The numbering is intentional:
5_6_0 ← Global objective #6
5_6_5 ← Media team's contribution to objective #6
6_5_5_1 ← Task #1 under that team objective
6_5_5_2 ← Task #2 under that team objective
9:30 — She Starts Work¶
Sam is online. They coordinate in the team room. Both ready to clock in.
Sam types first:
!start_work
Engelbot opens a multi-step wizard. Sam confirms the task ID, his role (Attacker), and that Asel is his Defender partner.
Asel does the same:
!start_work
Both clocked in. A session_id is generated. The work clock starts.
This is now logged in work_clock.csv with a START entry for both.
Layer 6 — Tasks
Tasks are the atomic unit of work. Every task has a budget, an Attacker, a Defender, and a status that moves through a defined lifecycle:
open → assigned → in_progress → review → complete
Nothing moves without Engelbot. Every transition is a ledger write, permanently auditable.
How this feeds the experiment
The START entry in work_clock.csv is timestamped. Combined with the eventual
STOP entry, it yields the Task Completion Velocity (Indicator 8) and,
when compared to task creation date, the Contribution Velocity (Indicator 3).
11:45 — They Stop Work¶
Two hours of focused work. Sam has written the script. Asel has reviewed it, flagged two factual errors about SC vesting rules, and Sam has corrected them.
Sam types:
!stop_work
Engelbot wizard: progress notes, checklist confirmation, handoff notes. Sam fills them in honestly.
Asel does the same:
!stop_work
Both clocked out. The session is complete.
session_logs.csv now has a full record. Status automatically moves to review.
12:00 — Waiting for Assessment¶
The captain reviews the session log, reads the progress notes, and checks the output. When ready, the captain runs:
!assess_work
Engelbot asks for three scores (1–10 each):
- Effort — How hard did they work?
- Learning — Did the work generate new knowledge?
- Collaboration — How well did Attacker and Defender work together?
| Total Score | Label | Payout |
|---|---|---|
| 27–30 | Excellent | 95% |
| 21–26 | Good | 85% |
| 15–20 | Adequate | 70% |
| 9–14 | Poor | 40% |
| 0–8 | Fail | 10% |
The captain scores: Effort 8, Learning 7, Collaboration 9. Total: 24 → Good → 85%.
Task budget was 50 SC. Payout: 42.5 SC. Sam (Attacker) earns 38.25 SC. Asel (Defender) earns 4.25 SC.
Both amounts land in pending-sc/transactions.csv — awaiting treasury validation.
How this feeds the experiment
The assessment scores (8, 7, 9) are stored in session_logs.csv.
They feed directly into the Task Assessment Distribution (Indicator 8).
Over time, the ratio of Excellent/Good/Adequate tasks shows whether coordination
is improving. The fact that this task completed on the first attempt
(iteration_count = 1) contributes to the Plan Effectiveness metric (Indicator 7).
14:00 — She Earns Some SK¶
After lunch, Asel notices a new owner in the workspace — someone who just completed
!ratify and is clearly confused about how !claim_task works.
She spends twenty minutes walking them through it in the general room.
Her captain notices. Later that afternoon:
!award_sk
The captain awards Asel 5 SK for peer mentoring.
Asel's SK balance: 72. Voting weight: 1.09.
Social Karma (SK) — The Currency of Trust
SK cannot be transferred, traded, or purchased. It is earned by being useful to the community:
- Mentoring new owners
- Contributing to governance discussions
- Writing documentation
- Completing tasks consistently (via captain awards)
- Peer nominations (
!kudos— coming in objective5_10_0)
SK decays 10% monthly. Stop contributing and your influence fades. This ensures that power tracks current service, not historical contribution.
How this feeds the experiment
The SK award is logged in social-karma/transactions.csv.
SK distribution over time is the basis for the Authority Concentration Index
(Indicator 4). A flat or flattening distribution over time supports the hypothesis
that power is genuinely distributing through earned contribution, not concentrating.
16:30 — She Applies for a New Role¶
The SC from today's session won't be validated overnight. But her captain sent her a note: there is a new Senior Attacker role open on the Media team. Three weeks of consistent Defender work, one session assessed as Good, and now a direct recommendation.
!apply
Engelbot wizard: which role, why she wants it, what she brings.
She writes carefully — this is a formal application, stored permanently in the ledger
at wiki/4_roles/4_2_5/applications/.
The captain will review it within the week. If approved, her role code changes from
4_3_5 to 4_2_5. Her SC earning share jumps from 10% to 90%.
How this feeds the experiment
Asel's application is a governance action. It will be logged in
governance-actions.csv. The time from application to decision contributes to
Decision‑Making Velocity (Indicator 8). The fact that a junior is progressing
to a senior role feeds the Capability Diversity Index (Indicator 3) and
demonstrates the horizontal career development the experiment is designed to enable.
17:00 — She Checks the Dashboard One More Time¶
!wallet
Engelbot returns her current state:
Alias: asel
License: Work
SC (pending): 42.50
SC (validated): 18.75
SK: 72
Voting weight: 1.09
Role: 4_3_5 (Junior Defender — Media)
Active tasks: 1
Not life-changing numbers. Not yet.
But every entry in that response is a permanent, auditable, tamper-evident record in a ledger that no single person controls.
She closes Element. She did something real today.
Your Day, Measured¶
Asel's ordinary Tuesday generated data points across nearly every indicator the experiment tracks. Here is what her day contributed to:
| CIQ Indicator | What Asel's Actions Measured | Data Generated |
|---|---|---|
| 1. Learning | Task completed without rework (iteration_count=1) | Evidence for improving Plan Effectiveness over time |
| 2. Memory | She used !show to reference the global objective structure |
Institutional memory accessed and navigated |
| 3. Integration | She collaborated with Sam (Attacker) as Defender | Cross‑functional pair logged in session_logs.csv |
| 4. Self‑Understanding | She checked her role, voted (abstained), and received SK | Authority distribution, role clarity, decision participation all logged |
| 5. Perception | She scanned the General Forum for external announcements | Environmental awareness captured in chat logs |
| 6. Threat Recognition | No crisis today — but the channel exists and is monitored | System readiness for anomaly detection |
| 7. Planning | Task completed on first attempt | Plan Effectiveness metric: task did not loop back to 'assigned' |
| 8. Coordination | Assessment scores (8,7,9), SK award, role application | Task Assessment Distribution, Resource Allocation Efficiency |
Every command she typed, every score she received, every governance decision she participated in — all of it became part of the experiment's permanent record.
This is how Smartup Zero turns daily work into evidence.
The Full Picture¶
| Layer | Name | What it is |
|---|---|---|
1_ |
General Forum | Public democracy — proposals, votes, transparency |
2_ |
Workplace | Coordination — objectives, ledger, big picture |
3_ |
Teams | Execution — 7 teams, each with a captain |
4_ |
Roles | Identity — what you are, what you can do |
5_ |
Objectives | Direction — global and team missions |
6_ |
Tasks | Action — the atomic unit of work |
| Command | What it does |
|---|---|
!whoami |
Your identity, roles, status |
!wallet |
SC balance + SK score |
!my_tasks |
Your active tasks |
!show [ID] |
Look up any entity — task, objective, role |
!open_roles |
Browse available roles |
!apply |
Apply for a role |
!start_work |
Clock in — begins paired session |
!stop_work |
Clock out — submits session for review |
!cancel |
Cancel any active command |
!help |
Full command list |
| Smartup Credits (SC) | Social Karma (SK) | |
|---|---|---|
| What it is | Wealth | Power |
| How earned | Task completion | Peer recognition + service |
| Decays? | No | Yes — 10% monthly |
| Transferable? | No | No |
| Redeemable? | Yes — €1 per SC | No |
| Grants authority? | Never | Yes — gates leadership |
Every task requires two people:
Attacker (Senior 4_2_X) — executes the work. Earns 90% of payout.
Defender (Junior 4_3_X) — oversees quality. Earns 10% of payout.
Neither can complete a session alone. Both must clock in, both must clock out.
The same triangle scales up through all layers of the organisation.
The point of all of this
Asel did not interact with a database today. She did not fill in a timesheet. She did not report to a manager or wait for approval from a hierarchy.
She typed commands. The ledger updated. The audit trail grew. Her contribution is permanently recorded, her earnings are traceable, and her growing reputation is visible to every other owner in the system.
And every one of those actions became a data point in an open experiment testing whether democratic ownership, shared memory, and constitutional autonomy actually make communities more collectively intelligent.
That is what a Smartup feels like from the inside.
Ready to start your own day at the office?