Open Commons ObservatoryEnglish·Русский

Понятия и решения

Понятия проекта и принятые решения — с тем, что было отвергнуто.

argenv is a star of OCO: gathered by its constellation, and the way every command line of the commons is declared. It is taken as tad is taken today - a pinned git dependency - and stays published on crates.io; it travels as a rhizcut when Rhizoid can make one.

The author, 2026-11-13: it keeps slipping our radar. It did because it was in no constellation - only an observatory that gathers everything held it - and kept no decisions; the rule about it (every tool declares with argenv, 2026-11-11) lived in OCO's place while argenv itself floated free. Checked the same day: of eight command lines, three are declared with it (snapall, lab-agent, oco-agent) and five are not (ocoeco, tad, the engine, devlab, tone). It is the ecosystem's own principle - declared once, as data, so it cannot drift - applied to how a program is told what to do.

Отвергнуто: Waiting for rhizcuts before using it everywhere (Rhizoid's command line is not yet built); leaving it outside any constellation (it would go on slipping).

2026-11-13

An input says where its values come from, and the contract gains one word for it: asked - known only when the program runs, and the program tells them. Whether a set is declared is read off allowed, as today; a list may have no allowed, and its members are then free, or asked. So: allowed given - declared; asked - one of whatever exists; neither - whatever the type admits. argenv answers one question from the contract - what fits here, given the words so far - calling the program's own function for an asked input and handing it what is already resolved. A program is asked from outside through the environment. Tab in a shell, a blank in a form, help (the question asked of an empty line), man pages and docs are surfaces of that one question; the shell's part is a few lines, the same for every program, made by argenv.

One need with three faces (issue 25; an id typed and refused three times in ocoeco's form; ocoeco's own free lists that cannot be declared), and the author's picture of entering: each relation selected, not entered; each stroke choosing what fits the next blank; being on a blank showing what can be entered. Prior art looked at first (research where-values-come-from): the world has come to declared-or-asked too, and asks the program through the environment.

Отвергнуто: A separate type for open lists (a type says what a value is, not where it comes from: it would double every type); a three-way source stored beside allowed (two places saying whether a set is closed can disagree, and a rule to keep them agreeing is a part to carry); a shell command named in the declaration, as usage's run= (the program is the one that knows, and a string is not checked by the compiler); a reserved command in the program's own space for asking; generating a script per shell with the candidates baked in (asked values cannot be baked); deciding now whether to emit a usage spec as an adapter (left to what friction shows).

2026-11-13