WEFT_OS/.agents/agents/continuous-simplicity.md

27 lines
1.4 KiB
Markdown
Raw Permalink Normal View History

docs: add engineering contract, contributor toolkit and templates Add AGENTS.md as the single engineering contract: sources of truth, evidence and proof requirements, ownership, working modes, the reviewed change loop, maintenance isolation, decision authority, dependency and fork rules, the 0.0.x to 0.1.0 release progression, and branch and publication rules. Add .agents/ with scope, implement, verify, maintenance and release procedures; reviewer, architecture debt scout, simplicity and refactoring roles; skills for the compositor, Servo rendering, runtime capabilities, appd sessions, packages and data, Linux deployment, integration verification and documentation; and verify.py, which runs the existing check profiles with --locked from any directory, stops on the first failure and supports --dry-run. check_toolkit.py validates local links and heading anchors, metadata, catalog coverage and issue forms. A new contributor-toolkit CI job runs both. The structure follows the Resina Design System toolkit at 1e768064f57a1e403ab271822383e732795905a6, adapted to WEFT. Validation, against the committed lockfiles: - verify.py toolkit: checker passes, 28 runner/checker tests pass - verify.py portable, demos, packages: pass - verify.py linux, runtime, servo-embed: fail on existing defects (clippy collapsible_if in the winit backend, three clippy lints in weft-runtime with wasmtime-runtime, and an E0308 in the selected Servo revision's servo-layout); the runner reports the failing status Add CONTRIBUTING.md, issue forms for defects and changes, maintenance problems and decisions of direction, and a pull request template asking for ownership, proof and the validation actually performed. README.md links the contribution guide.
2026-10-08 23:40:08 +00:00
---
name: continuous-simplicity
description: Remove one evidenced duplicated decision, unnecessary state or misleading fallback path while preserving WEFT OS behavior and ownership.
---
# Continuous simplicity
Run through [maintenance](../commands/maintenance.md) under the contract's
[maintenance rules](../../AGENTS.md#8-maintenance). Establish the affected
caller, contributor or contract, the present cost and the acceptance criterion
before changing anything.
Candidates are concrete: the same decision computed in two places, state that
can disagree with its source, a fallback that hides a failure or reports success
it did not achieve, an obsolete path, indirection without a second caller, or
documentation that restates and contradicts code. Prefer deletion and existing
concepts. Do not optimize for line count, merge distinct privileges or failure
domains, or replace explicit errors and authority checks with something shorter.
Removing a misleading fallback can change observable behavior from silent
success to explicit failure. That is in scope when the fallback contradicts the
contract; state the change and prove the new failure mode.
Establish preservation evidence first, implement, run [verify](../commands/verify.md)
and have the [reviewer](reviewer.md) inspect the committed range. Stop after one
issue and pull request result; simplification never becomes the primary goal.