You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-7Lines changed: 18 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ You choose the LLM. You own the data. You control the deployment. Zaati OS has n
36
36
## What makes it different
37
37
38
38
-**Any LLM workflow:** ChatGPT, Claude, Gemini, a local model, n8n, cron, or custom code can publish the same contract.
39
-
-**LLM-directed presentation:** A safe UI contract lets the producer request metrics, lists, timelines, calendars, lineor bar charts, progress views, notices, text, and tables. The renderer only permits audited components, never arbitrary HTML or code.
39
+
-**LLM-directed presentation:** A safe UI contract lets the producer request metrics, lists, timelines, calendars, line, bar, or allocation charts, progress views, notices, text, and tables. The renderer only permits audited components, never arbitrary HTML or code.
40
40
-**Private by architecture:** Real snapshots are ignored in the public code repository. The recommended public-fork setup keeps data in a separate private repository and protects the deployment with Cloudflare Access.
41
41
-**Files before databases:** JSON is portable, diffable, inspectable, and easy for AI tools to create.
The first demo visit opens an optional guided tour of sources, safe components, scheduled-task prompts, and the private setup path. Everything shown is public synthetic data. When you are ready to create your workspace:
57
+
58
+
```bash
53
59
npm run setup
54
60
npm run tutorial
55
61
```
56
62
57
-
The setup assistant creates ignored local preferences. The tutorial runs a credential-free mock LLM that deliberately fails its first contract attempt, retries safely, creates six synthetic snapshots in one transaction, and opens the dashboard.
63
+
The setup assistant creates ignored local preferences and switches the local app to private mode. Synthetic example pages, Component Lab, copy-prompt guides, and the automatic demo tour are no longer included. The tutorial can still test ingestion with credential-free synthetic snapshots, clearly labeled as test data inside the private shell.
58
64
59
65

60
66
@@ -69,12 +75,15 @@ make tutorial
69
75
70
76
## Make it yours
71
77
72
-
1. Fork the code repository and run `npm run setup`.
73
-
2. Test the entire ingestion loop with `npm run tutorial`.
74
-
3. Run `npm run prompt:create`, then paste the generated task prompt into the LLM you already use.
78
+
1. Explore the synthetic demo and guided tour with `npm run dev`.
79
+
2. Run `npm run setup` to create an ignored private workspace and remove demo-only UI.
80
+
3. Test the entire ingestion loop with `npm run tutorial`.
81
+
4. Run `npm run prompt:create`, then paste the generated task prompt into the LLM you already use.
75
82
76
83
Everything else, including custom sources, encrypted storage, full theme tokens, and automatic deployment, is optional and documented separately.
77
84
85
+
Synthetic demo mode includes a **Component lab** with the JSON contract beside each rendered block. Every demo source also includes a **Recreate this page** drawer containing one standalone scheduled-task prompt. It includes the resolved worker and source, permission boundary, and current executable schemas; the user only replaces the code repository, private data repository, and timezone placeholders before review and use.
86
+
78
87
The canonical daily bundle contains agenda, inbox attention, work focus, money, news, and the dependency-backed daily overview. Prompt Studio can also create smaller independent bundles, and now generates the matching private-repository setup command.
79
88
80
89
## Create a scheduled task prompt
@@ -155,7 +164,7 @@ See [LLM contract](docs/llm-contract.md) and [`schemas/`](schemas/) for the exec
|`weekly-review.md`| Find patterns and produce an evidence-based review | Progress, timeline, decisions |
157
166
158
-
These are provider-neutral templates, not connectors. ChatGPT scheduled tasks are the target first real path, but the release evidence is not complete yet. Other providers are contract-compatible and are not claimed as end-to-end certified until their documented release gate passes.
167
+
These are provider-neutral templates, not connectors. The local mock tutorial and command adapter are maintained in v0.1.1. ChatGPT scheduled tasks are the target first hosted path, but no hosted provider is claimed as end-to-end certified until its documented provider gate passes.
159
168
160
169
## Repository map
161
170
@@ -236,7 +245,9 @@ Zaati OS charges no platform fee and can be deployed using free or already-owned
236
245
237
246
Code version: **v0.1.1**
238
247
239
-
No immutable GitHub Release is published yet. Until the recorded provider and hosted-demo release gates pass, pin private validators to a reviewed full commit SHA. This code version establishes the portable data contract, atomic bundle ingestion, adaptive renderer, guided onboarding, provider-neutral prompts, optional encrypted storage, theme studio, privacy boundaries, Cloudflare recipe, and CI quality gates. See [CHANGELOG.md](CHANGELOG.md).
248
+
Latest GitHub release: **[v0.1.1](https://github.com/mohsinht/zaati-os/releases/tag/v0.1.1)**, published August 25, 2026.
249
+
250
+
This foundation release establishes the portable data contract, atomic bundle ingestion, adaptive renderer, guided onboarding, provider-neutral prompts, optional encrypted storage, theme studio, privacy boundaries, Cloudflare recipe, and CI quality gates. Hosted LLM workflows remain contract-compatible rather than provider-certified until their recorded end-to-end gates pass. Private validators should pin the reviewed v0.1.1 release commit `0ef31dc8e973e5f1f557b1df9c7f79a012dd7d2a`; future signed, protected, and immutable releases may be used as stable references. See [CHANGELOG.md](CHANGELOG.md).
240
251
241
252
Before storing real data, read [Data lifecycle and key recovery](docs/data-lifecycle.md). Fork maintainers can follow [Upgrade and fork sync](docs/upgrading.md).
"summary": "One scheduling decision and one document review need a response. Everything else can wait.",
17
+
"title": "Four messages fit into two reply windows",
18
+
"summary": "One deadline and one scheduling decision come first. A review and follow-up can share the afternoon window; 18 low-value messages remain excluded.",
0 commit comments