sharness.ai / admin / comms
Comms: tasks & requests
Numbered so they can be referred to from any page, commit or conversation. A request (R) needs a decision or input from the project lead; a task (T) is work anyone can pick up.
| # | Item | Status |
|---|---|---|
| R1 | The one-paragraph statement of what SHarness is and who it is for. Supplied by the design pack's brief; the front page, llms.txt and the CLI README now carry it. | done |
| R2 | Repository settings for the deploy: Pages served by GitHub Actions, custom domain sharness.ai over HTTPS, and the github-pages environment allowing deploys from dev. Confirmed by the first release, v0.1.0, which deployed from dev and serves at https://sharness.ai. | done |
| R3 | Review the design pages against the source pack before they are used to brief the building agents. Especially: the claim labels (measured / designed / not yet measured), the renaming of sgit-* components to sharness.*, and the published observations of the Claude workspace on Evidence §7. | needs review |
| R4 | Command name: sharness-ai, decided 24 Oct 2026. Applied on the CLI's dev branch (the sharness shorthand removed); ships with the next CLI release. | decided |
| R5 | Read the two articles. A secure harness for agents is written in Dinis's voice from voice memo 01 and he has not read it yet; two phrases of the transcript were left out as unclear. What shipped on day one is the build agent's own. | needs review |
| T4 | The memo's acceptance test as a runnable example: a hello world with Claude inside SHarness, showing no internet and no file-system writes. Depends on the first components. | open |
| T1 | Run the process-tree proof of concept and publish its results on Evidence (roadmap decision 6). | open |
| T2 | Fix the known issues in the source pack (a broken link, mixed component names) in the next revision of the pack; the published copy stays verbatim. See the list. | open |
| T3 | Pages for the CLI's commands as they are built, each with a markdown twin. | open |