iotone-oss/modularry

iotone-oss/modularry hg public

modularry

iotone-oss

45 files284.7 KB in thembiggest 27.6 KBdocs/DESIGN.md133.9 KB on disk, history and all

vitality newempty: no commit. new: made less than 30 days ago. active: a commit in the last 30 days. steady: in the last 90. quiet: in the last year. dormant: nothing in a year.4 commits in 90 daysone pair of hands

AI: ask first · automated collection is not permitted until the owner is asked and says so · this instance's default; nobody has said yet

0 saves by 0 peoplesign in to save

README.mdiREADME The file a repository's page shows as its front page, if there is one at the top of the default branch. Write it for the person arriving without context: what this is, who it is for, and what to do first.

%ularry

A terminal assistant for planning Eurorack modular synthesizer racks, written in Pop-11 and run on Poplog.

The first four build steps are in place. %ularry loads a rack file, draws it, and checks its power, fit, depth, cost and coverage. You can talk to it in plain sentences, and stage, review and apply changes to the rack. With Ollama running it uses a local model to understand sentences and to answer in words; without it, it goes by keywords. It can drive a Chrome window to show your ModularGrid racks, import one, open a module search, and show a plan before and after. The ModularGrid side has not yet been tried against the live site; see docs/NOTES.md, "Unverified".

docs/DESIGN.md: the running specification, with what is built and what is planned
docs/NOTES.md: design notes, findings and open decisions

Running from a checkout

You need a built Poplog. It is looked for in $POPLOG_HOME, then in a poplog directory beside this checkout. macOS and Linux only.

bin/modularry examples/racks/demo.json

you> what is the rack missing?
you> how is the power?
you> move the filter to col 40
you> yes
you> :plan
you> :why
you> :help

A local model (optional)

ollama pull qwen2.5:7b

%ularry finds Ollama at http://localhost:11434 by itself. :models shows what is in use. MODULARRY_OLLAMA_MODEL and MODULARRY_OLLAMA_URL choose another model or server, and MODULARRY_MODELS=off switches models off. The model never supplies a figure: every number comes from the rules.

The browser (optional)

Needs Node 18 or later and Google Chrome.

tools/setup-browser.sh

you> :login
you> :racks
you> :open 1234
you> :import
you> :preview

:login opens Chrome with a profile of its own, at ModularGrid's sign-in page. You sign in by hand; %ularry never sees your password and does not type into the site. It opens pages for you and reads your own racks when you ask. It changes nothing on ModularGrid.

Tests

tools/test.sh           # every suite, then the launcher
tools/test-browser.sh   # real Chrome, headless, at a local page
tools/eval-routing.sh   # routing accuracy against a local model

Layout

Path	Holds
`src/mr_rack.p`	The rack model and its JSON file format
`src/mr_rules.p`	Power, fit, depth, cost and coverage rules
`src/mr_draw.p`	Rack picture, module list and report panels as text
`src/mr_plan.p`	The change plan: staged adds, moves and removes
`src/mr_tools.p`	Every action, in one table
`src/mr_args.p`	Module, row, column and file out of a sentence
`src/mr_talk.p`	Sentences: routing, confirmation, the ELIZA engine
`src/mr_model.p`	Routing and phrasing by a local model, through Ollama
`src/mr_site.p`	The browser helper's client, and ModularGrid's addresses
`src/mr_browse.p`	The browser tools: sign-in, racks, import, search, preview
`src/mr_import.p`	A rack from ModularGrid's page data
`src/mr_html.p`	The plan as a before-and-after page
`helper/`	The Node program that drives Chrome
`src/mr_state.p`	What a session remembers
`src/mr_repl.p`	Colon commands and the read loop
`scripts/modularry.txt`	%ularry's ELIZA script
`src/modularry.p`	Entry point
`bin/modularry`	Launcher
`tests/`	Test suites
`tools/`	Test and measurement scripts, and `setup-browser.sh`
`examples/racks/`	Example rack files

about this project

clone: https://spicemine.iotj.cc/iotone-oss/modularry
engine: Mercurial (hg)
visibility: publicivisibility Who can see a repository. Private: only the writers and admins of its space. Members only: anyone can find it in its space and read its showcase - the title, the description, the public journal posts - and the files, history and clone address are for members of the space. Public: anyone at all, everything. New repositories are private, because a store that holds unreleased work should not be the kind of place where something escapes by accident. What you may not see is not listed at all - not greyed out, not refused.
created: 2026-11-14 03:26 UTC
last change: 2026-11-14 03:12 UTC
visits: 4 · 4 peopleRequests for this page since 0.112.0, and how many the guardian took for people: signed in, or anonymous with a client it could name, standing allowed, and no crawler's user agent. A request it could not judge counts as a request and not a person.
history received: 7
mirrors: none
tags: none
rating: not counted yetRatings will come from links between projects, which do not exist yet.
history sent: not counted yeta clone or a pull from here