8000 Restore the owner's Aladdin design system on the README and site; real quick start by adeelahmad · Pull Request #126 · adeelahmad/aloop · GitHub
[go: up one dir, main page]

Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
4c6ba45
Brand: adopt the Aladdin design system (README, site, banners, social…
claude Oct 20, 2026
b05edd4
Brand review fixes: no emoji left, disc and card contrast, exact bar …
claude Oct 20, 2026
5ad7a7a
Merge #94 (the owner's Aladdin design system) onto master
claude Nov 20, 2026
8f9884f
README and site lead with the owner's brand; the site's quick start i…
claude Nov 20, 2026
e7c959d
Site: the Aladdin design system applied as given
claude Nov 20, 2026
70b2c22
Site: build your own pack (kernel, kernel extensions, user space), co…
claude Nov 20, 2026
9c55898
Merge origin/master (#124 M12.1-M12.6) into the branding branch
claude Nov 20, 2026
bb08e66
Site: the pack section in the nav; site.test.py pins it
claude Nov 20, 2026
ba0584c
Site: Build your own Module (harness = hardware, aloop = kernel, modu…
claude Nov 20, 2026
51a0206
aloop is a kernel for your harness: README and site headline; modules…
claude Nov 20, 2026
c9de87b
Site: a shorter lead under the kernel headline
claude Nov 20, 2026
f23a751
Site: modules and distros with #127's final commands, each run on its…
claude Nov 20, 2026
cef4867
Site: GA4, off until a measurement id is listed; several ids for seve…
claude Nov 20, 2026
6b1e1ed
Site: the owner's Google Tag Manager container (GTM-NTRH49WJ) beside …
claude Nov 20, 2026
8dbbbf2
Merge origin/master (#127 modules and distros, #118, #111) into the b…
claude Nov 20, 2026
d859beb
Merge origin/master (#125 M11.15, the owner's CNAME); the site's cano…
claude Nov 20, 2026
1dd9e4a
site.test: the canonical link to the CNAME domain is not an external …
claude Nov 20, 2026
4ecbbe7
Site: the canonical link is a void tag
claude Nov 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ tag in lockstep. Tag releases as `vMAJOR.MINOR.PATCH`.
## [Unreleased]

### Added
- The README and the site lead with the owner's brand again (ROADMAP §4.11): #94, the owner's Aladdin design system, had sat unmerged since 2026-10-20, so master still carried the earlier invented gold kit; it is merged here, and the owner's Aladdin's loop infographic (`docs/diagrams/aladdins-loop.webp`, genie included, as given) now heads the README and the site. The site's hero command was a shell `aladdin "add CSV export to the report"`, which only records an intent; the site now has a quick start with the real install lines and `/aladdin Add rate limiting to the API` (the infographic's example; each line run on Claude Code 2.1.329 against the GitHub marketplace), and the roadmap through M12. Tests: `site.test.py` (the brand assets, the quick start's commands, the roadmap; red on the old page), `readme.test.py` (the infographic leads).

- **Kernel and user space (M12).** The loop's opinions (16 roles, skills, a kernel reference) are
ejected into `docs/agents/userspace/` (tracked in git) on the first session or `aloop init --apply`,
and changed freely. `aloop userspace` (`status`, `which`, `upgrade`, `diff`, `merge`, `accept`,
Expand All @@ -43,7 +45,7 @@ tag in lockstep. Tag releases as `vMAJOR.MINOR.PATCH`.
- Core agent principles and the one-way / two-way door rule (ROADMAP §4.12, M9.30): seven core principles from Amazon's Leadership Principles, the door rule first, go to every aloop agent at session start (`aloop mission principles show --core`). A two-way door (a branch, a local edit, a test, a draft PR) is decided, not asked. A one-way door (`aloop mission doors list`: a push or merge to the default branch, a force-push, a release, a deploy, a message sent outside, a secret, dropped data, …) is stopped by a PreToolUse gate with `ASK[door] <id>` until the human records an authorization in their own terminal (`aloop mission doors authorize ID --by NAME --reason TEXT [--until DATE] [--once DIGEST]`, a hash-chained ledger row); a wall (switching a gate off, forging a human record) is never crossed. While a run is live, a question to the human must name a door the gate stopped and nobody authorized. Reason: Adeel's request that agents decide two-way doors themselves and ask only at a one-way door not already authorized. Test: `mission-doors.test.py`. Hardened by an adversarial review (15 findings, each a test): the gate reads Bash as the shell does (comments, line continuations, heredoc bodies, `xargs`, `find -exec`, `echo … | sh`), a branch condition reads the directory the command acts on (`git -C`, `cd`), settings are guarded wherever they live, dry runs and `command -v` are two-way, the newest decision by time counts and a revoke holds on every branch, a once-grant is crossed once under a lock, a broken ledger is named, and `doors authorize` refuses an agent's shell.
- DeepSeek Harness (dsh) host (ROADMAP §4.9): `aloop install dsh` (alias `deepseek`; `--project P` or `--global`) renders a `dsh --profile aloop` profile in `$DSH_HOME` and installs the skills. Its native plugin (`plugin/hosts/dsh/aloop.mjs`) runs the same gates as Claude Code on dsh's own events: a deny before a tool runs, a block after an invalid artifact write, and a stop gate that steers a role back up to 3 times before the supervisor is told it is BLOCKED (or STUCK, released unverified). Roles are agent presets on two subagent tools, one per model route (`deepseek-v4-pro` for planning, `deepseek-flash` for work by default; `MODEL_PLANNING_DSH` / `MODEL_WORKER_DSH` override). A writer's `aloop bind` moves its working directory into its worktree, and `host-adapter` confines its commands, edits and `working_directory` there. Usage is recorded Claude-shaped per role, so budgets, the ledger and `run-summary` work unchanged. `make e2e-live HOST=dsh` drives it live and exits 2 with the fix when no `DEEPSEEK_API_KEY` is set. Reason: DeepSeek's own harness is the cheapest route to a strong model. The profile records the project it serves (or `--global`), so another project's `aloop-init` never re-renders it, and gates get the worker shell's environment (no API key). The mission layer's six roles run on dsh too: presets on their route group's subagent tool, `gate-mission-scope` on every write and command, and `gate-mission-artifact` at each role's start and stop; the mission skill installs as `aloop-mission`. A second review (3 lenses; 11 confirmed findings, each fixed with a test) closed: a working directory that vanished (dsh's tools move it back to the main tree, so the plugin judges `ensure()`'s directory and `host-adapter` refuses to run from a missing one), gate switches from the project's `.env` (dsh loads it; `SKIP_HOOKS`, `GATE_RUN_TESTS`, `REPO_DIR`, `AGENTIC_*` from it never reach a gate), an interrupted Stop that dropped the sprint-close notice, and the shared profile: its owner is the main tree, an older unrecorded profile is claimed only by the project that installed it, and a project it does not serve is told so by `install status`, `aloop-init` and the session itself. Tests: `dsh-plugin.test.mjs` (48 checks, emulated), `dsh-runtime.test.mjs` (53 checks on the real pinned dsh 0.2.1-rc.2 with a scripted model; the CI hosts and macos jobs install it) and `dsh-install.test.py` (10).
- dsh follow-ups (ROADMAP §4.9). One `aloop install dsh` serves every project: the plugin routes each role's requests through dsh's `agent/request` to its own project's model (`aloop models resolve <role>`), so gate-dispatch no longer refuses another project's roles until a re-install, and a role whose model cannot be resolved is refused (fail closed). Roles are no longer offered `send_message`, so dsh adds no "send your result" guidance and no call is spent on a deny. dsh compaction is recorded as `context.compacted` and the handoff comes back after it; the capability matrix marks dsh compaction and live messaging as advertised, proven on the real runtime. Two mission roles (one per subagent tool) run through both of their gates on the real runtime. `run-summary --host dsh` reports a dollar cost: each logged call is priced from a dated, sourced DeepSeek table (`plugin/bin/_prices.py`; cache hit, cache miss, output, peak or off-peak), with `cost_by_model` in `summary.json`; an unpriced model id keeps its tokens and leaves the cost unmeasured, never guessed.
- Brand kit and repo front page: `docs/brand/` holds the mark (an **a** whose bowl is a red-to-green loop passing a gold gate, with a 16 px cut), lockups, light and dark README banners, favicons, app icons, the site's OG card and the GitHub social preview, all generated by `docs/brand/gen_brand.py` from one palette with WCAG checks (rules in `docs/brand/README.md`). The README leads with the mission layer, the agent principles and the door rule, the supported hosts and the measured demo runs; the site carries the favicon and Open Graph/Twitter card metadata; `SECURITY.md` and bug/feature issue forms are new.
- Brand kit and repo front page on the owner's **Aladdin design system** (vendored in `docs/brand/design-system/`: tokens, guidelines, the social preview and OG card sources): the wordmark (DM Sans 800 over the blue-red-green-gold loop bar) and its on-blue variant, the four-dot signature, an icon with a 16 px cut, light and dark README banners, favicons, app icons, the site's OG card and the GitHub social preview, all generated by `docs/brand/gen_brand.py` from the design system's colour tokens with WCAG checks (rules in `docs/brand/README.md`). No emoji on brand surfaces. The README leads with the mission layer, the agent principles and the door rule, the supported hosts and the measured demo runs; the site carries the favicon and Open Graph/Twitter card metadata; `SECURITY.md` and bug/feature issue forms are new.
- The mission loop hands out a goal's commands only when the gate takes them (ROADMAP §4.12, M9.53): before `PLAN_INTENTS`, `mission tick` runs the same `goal check` that `goal intents` runs, before `SPRINT` all of what `goal next` checks (the next intent's `intent check` included), and before a met goal's close it asks `goal close`'s own rule. The loop's check of the next intent runs in process, so `tick --peek` and `due` still record nothing (no `intent.normalized`); a goal with no intent to hand out, or a next intent whose check crashes, is `BLOCKED` with that reason. A refusal is `BLOCKED` with the gate's reason (for example "the mission changed since the goal was derived"), where the loop used to hand out the same command 3 times and then block naming no cause. `goal close` now checks the ledger and the goal's content before it trusts a `goal.met` record, records `goal.met` before it sets the status, and repairs a bare `met` status; `goal next` refuses a goal with a `goal.met` record. Test: `mission-tick` check 34 and `mission-goal` check 8; every goal in the tick suite that reaches a goal command is now a real one, derived through `aloop mission` on the project's clock.
- A goal its sprints did not meet is retired, and the loop moves on (ROADMAP §4.12, M9.50): `aloop mission goal retire GOAL --eval EVAL` records `goal.retired` in the committed ledger once every intent of the goal was sprinted and its sprints closed, and the newest eval of it, made after those closes from a state measured after them, still lists gaps. A retired goal takes no more intents, sprints or close. `mission evaluate` covers the whole mission again, and the retired goal's own open gaps are held from the next goal until a new baseline version or the human's next approval of the mission, so the loop does not sprint the same gaps again; a regression is never held. When every gap is held, `mission tick` says `BLOCKED` and the human's `aloop mission tick --force --by NAME` lifts it. `mission tick` hands this out as `RETIRE_GOAL` (role `mission-planner`) where it used to stop at `BLOCKED` for the human. It asks the command's own rule first: a stale state or eval becomes `ASSESS` or `EVALUATE`, and any other refusal is `BLOCKED` with its reason. 3 retired goals in a row still go to the human. The planner's stop takes a retired goal as its finding. Tests: `mission-goal` check 13, `mission-tick` checks 28 and 33, `mission-roles`.
- A mission's gap lists count only as `mission evaluate` computed them (ROADMAP §4.12, M9.27): `evaluate` records `eval.completed` in the committed ledger, and `mission tick`, `evaluate check` and `goal` take the newest eval whose content that record covers, with a matching seal, in the ledger's order. An eval file written by hand, or edited (or re-stamped) after it was recorded, no longer sends the loop to `RESEARCH` as "goal met" or makes `goal derive` refuse what tick handed out, a clock that is behind no longer reorders them, and a fresh checkout derives and closes goals from the evals it committed. An eval or state named as journey or baseline evidence needs its record too. Tests: `mission-tick` check 32, `mission-journeys`.
Expand Down
Loading
Loading
0