@lapxo/bound 0.1.0

package/CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing to Bound
+
+Bring a counterexample, an observation or a proposed lot. Include the inputs and the output that led you to it. A signature establishes who was authorized to speak; it does not make their result true.
+
+## Set up a working copy
+
+Clone the repository and use the Node version supported by package.json. If package-lock.json is present, run npm ci; otherwise use npm install --ignore-scripts --no-package-lock. Then run:
+
+```sh
+npm run build
+npm test
+```
+
+These are development checks, not project acceptance. For a place with admitted trust context and native receipts, run the product judgement as well:
+
+```sh
+npx @lapxo/bound@0.1.0 fold --check
+```
+
+Preserve a refusal and its exit status in your report. Do not borrow a neighbouring checkout's ledger or substitute local bytes for a named pin.
+
+## Make the smallest useful change
+
+Bound owns admission, folding and evidence. Topos owns grammar, forms, classes, views and their contracts. A selected topos owns domain measurement. Obligations owns the algebra. Keep each change in its layer; do not put a domain decoder, path-based inference or a fallback for a missing pin into Bound.
+
+An algebra change needs an independent oracle and a counterexample. A host change needs evidence for authentic bytes, failure propagation or reuse. A view change needs its declared region and implementation identity. A test should fail for a plausible incorrect implementation, not assert a source string or repeat the same expression on both sides.
+
+Keep regressions for changed signatures, unauthorized coverage, exact-id withdrawal, conflicting evidence, local versus travelling acts, corrupt content and duplicate delivery. Consolidate repeated setup and duplicate scenarios without removing distinct falsifiers.
+
+## Propose and admit
+
+Keep proposal and signed-lot files outside the repository. Use the current admitted wire, by=target, and no preassigned epoch or signature. The team's admitted key signs the lot; Bound admits it under scope coverage. The [usage guide](docs/usage.md) explains the transaction and external key-file requirements.
+
+Send the proposed lines with the leaf changes they render. A hand-edited render is evidence of the intended change, not an admitted contribution. Do not edit the accepted TARGET to make a test or ceiling pass. If a render disagrees with the lock, fix the proposed lines and re-render it.
+
+Commit only the project's TARGET.bound and native receipts.bound as bound files. The first .gitignore line excludes .bound/. Do not commit keys, stores, ledgers, caches, capsules, archives or vendored dependencies.
+
+## Submit a pull request
+
+Explain the concrete behavior before and after the change, the affected layer, and the checks you ran. Include stdout, stderr and exit status for a CLI case. State which reader and input bytes produced the evidence; a source harness is not an installed-package proof.
+
+Policy changes receive explicit team review separately from measurements of the proposed source. Keep incompatible readings and their origins visible. Never remove a failing test or weaken a ceiling to obtain acceptance. Withdraw statements through their admitted history; do not rewrite prior signatures, tags or releases.
+
+Documentation and workflows follow the same review: propose their lines and include the rendered changes.

package/LICENSE

@@ -0,0 +1,22 @@
+the license this place is bound by
+MIT License
+
+Copyright (c) 2026 Lapxo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,97 @@
+# @lapxo/bound
+
+![license MIT](https://img.shields.io/badge/license-MIT-)
+
+Declare what must hold. Read what does. Keep the evidence
+
+```bash
+npx @lapxo/bound@0.1.0 fold --as help
+npx @lapxo/bound@0.1.0 fold
+```
+
+## How Bound reads a project
+
+## A meeting everyone can understand
+
+Ana is available from 10 to 14, Luis from 12 to 16, and the room from 10 to 13. Their common availability is 12 to 13. A boss available from 18 to 20 makes the encounter incompatible. Withdrawing that exact reading restores the overlap; Ana, Luis and the room remain.
+
+With an interval form, those are object operations: observe independent claims, meet them, withdraw by id, and read the state. A narrower compatible meet is not a fork. Folding a file of declarations alone does not calculate meeting availability.
+
+The same pattern applies to a delivery window, a sensor's allowed range, or an agreed performance budget. The chosen topos determines the units and how evidence is obtained. Bound does not supply a meeting-specific rule.
+
+## See how information holds together
+
+![Cells, travelling bounds and a local join](docs/readme-assets/atlas.svg)
+
+A travelling ceiling on B reaches C and G through their declared rest. A local join widens B alone. D is independent. The figure shows those relations; point size and camera distance do not measure information.
+
+| State | Meaning |
+| --- | --- |
+| REQUIRED | Compatible bounds, fewer than two independent origins. |
+| FREE | Independent origins meet and their encounter fits the bounds. |
+| CONFLICT | Bounds conflict, or eligible claims have no common encounter. |
+| FORBIDDEN | An inhabited encounter does not fit the bounds. |
+
+Bounds are checked before origins and claims. A receipt is evidence of a reading, not another origin. Duplicating one does not add freedom.
+
+## Change a project without erasing evidence
+
+Work in the project's directory. Use an existing admitted key identifier and its matching private key stored outside every repository. Your public key and coverage belong to the authority contract; possession of a private key alone does not authorize a scope.
+
+```sh
+export BOUND_KEY_ID='your-admitted-key-id'
+export BOUND_KEY_FILE="$HOME/Private/keys/your-device.pem"
+lot_dir="$(mktemp -d)"
+```
+
+Have the selected view produce a proposal at `$lot_dir/proposal.bound`, or prepare the project's permitted lines there for review. Unsigned proposals use `by=target`, without a preassigned epoch or `sig`. Lots stay outside the repository; the committed bound files are only `TARGET.bound` and `receipts.bound`.
+
+```sh
+npx @lapxo/bound@0.1.0 sign "$lot_dir/proposal.bound" \
+  --key "$BOUND_KEY_ID" --key-file "$BOUND_KEY_FILE" \
+  > "$lot_dir/signed.bound" &&
+npx @lapxo/bound@0.1.0 land "$lot_dir/signed.bound" &&
+npx @lapxo/bound@0.1.0 fold
+```
+
+`sign` assigns the admitted epoch and writes the signed lot to stdout. `land` validates the whole lot before admission. A refusal is evidence to inspect; it is not success. Do not proceed after a failed signature or admission. The key file is a PKCS8 private key matching the admitted public key; do not put it in the lot, source tree, package or CI artifacts.
+
+For typed object withdrawals, `takes` names the exact claim or mark id. Removing a local join leaves the travelling sign live. For untyped configuration, use the wire's exact withdrawal selectors; do not combine withdrawal and replacement with identical selectors in one lot. Wire alphabet updates supersede by epoch.
+
+[Authority, withdrawals, receipts and PR review](docs/usage.md).
+
+## Select a topos by what it declares
+
+`sources/<name>` says where a world can be obtained. An admitted `uses/<name>` names the digest of that topos's folded standing: canonical live claims in wire byte order, excluding signature envelopes and host shape. Re-signing the same standing preserves the pin. A changed live form, class, view or offer changes it.
+
+`restsOn` closes artifact bytes separately. A capsule is one offer. Forms, classes and views need no capsule merely to be selected. Runtime and packing do not define standing identity. npm dependency ranges remain package metadata; they are not standing pins.
+
+| Responsibility | Owner |
+| --- | --- |
+| Meet, state, live acts and rest | Obligations |
+| Wire, forms, classes, views and offer contracts | Topos |
+| Admission, folding and evidence | Bound |
+| Domain measurement and representation | Selected topos |
+| Storage, transport and execution | Host |
+
+Cell `restsOn` is the object's relation. Directory prefixes and file summaries are host coordinates, not object rest. Wire tokens are protocol constants, not organization, host, path or key literals.
+
+## Repository rules
+
+Commit `TARGET.bound`, `receipts.bound` and the outputs the forge reads. Ignore `.bound/` from the first line of `.gitignore`. Keep proposals, signed lots, keys, ledgers, caches and dependency blobs outside the published tree.
+
+The lock is the project's own contract and pins. Read a dependency's declarations from its selected standing; do not copy its lines into your lock. README, package metadata and workflows must be renders of admitted declarations. A scan is an observation, not permission to lower a ceiling.
+
+A PR proposes lines and the leaf changes they render. The judge uses the team's accepted contract independently of the proposed revision. Preserve refusals, conflicting origins and unpaid demands. [Repository and contribution rules](docs/usage.md#repository-and-pr-review).
+
+## An atlas you can question
+
+Information can share a history without sharing a single presentation. The same admitted cells can support a compact status view, a spatial view of their relations, or a focused reading of one disagreement. Each view asks for a region and resolution; its selected topos determines the representation.
+
+This makes changes inspectable. A local act can remain local, travelling bounds can reach dependent cells, and a receipt can name the inputs of the reading you saw. You can ask what changed and what depends on it without turning a drawing into the algebra.
+
+A pin names standing, not a download URL or runtime entry. Its declared artifact dependencies close the bytes needed for an offered operation. The boundary lets a form or view remain meaningful even when it has no executable capsule.
+
+Use Bound where independently attributed observations must be judged against an accepted contract: compatibility between components, operational limits, or a team's project requirements. The selected topos must supply the actual measurements; a digest identifies the evidence without declaring it true.
+
+[Contribute a counterexample or a proposed lot](CONTRIBUTING.md).