Skip to content

Create the copying module, and decide how it holds a key the venue can take back - #32

Merged
napkinstack-agent[bot] merged 1 commit into
mainfrom
module/copying
Sep 24, 2026
Merged

napkinstack-agent[bot] merged 1 commit into
mainfrom
module/copying

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

Create the copying module, and decide how it holds a key the venue can take back


Module

modules/copying — exactly one.

  • This pull request touches a single module
  • ⚠️ Cross-module — the cross-module label is required, justification below

The only file outside the module is the CODEOWNERS line the scaffolding adds.

Deliverable

Deliverable: D2

This pull request changes no module beyond its description — manifest, AGENTS.md,
README.md, docs/ — so it is not delivery work in the check's sense. D2 is named because it
is what the module exists for.

What it changes

Cycle 03 says copying is created when the cycle is accepted; it was accepted today. This is the
module's description and its founding decision, before any code, so the decider can refuse
the shape of the thing that holds members' keys before it exists.

ADR-0001 (proposed) decides:

  • flet generates one agent key per member and never touches the main key. The member
    approves flet's agent on the venue's own API page, named flet valid_until <30 days>.
  • The venue is the record. There is no revoke action on the venue: an agent dies by expiry or
    by replacement under its name. So revocation is the member's act on the venue, and flet reads
    extraAgents before every action, doing nothing — and not retrying — when its agent is absent
    or expired.
  • A fresh address every time: a deregistered agent's nonces may be pruned, which makes its old
    signatures replayable.
  • At rest: Fernet under a secret from the environment, mode 0600, deleted once the venue no
    longer lists the key. Stated plainly: this protects a leaked file or backup, not a
    compromised server.
  • Dependencies: hyperliquid-python-sdk 0.24.0 and cryptography, each with its exit.

Taken by the decider on 2026-09-24: the venue's page over a signing page of ours, 30-day expiry,
testnet with a wallet they fund.

What the venue does not document is written as such, not papered over: the unit of
valid_until, extraAgents itself (SDK only), and any list of what an agent may sign. D2's tests
establish each by asking the venue.

Oracle

docs/os/05-workflow.md §3

  • The success criterion was written before the implementation
  • It was seen failing, for the right reason
  • It passes now

Kind of oracle: fitness function — nstack fitness compliant, including the manifest's
one-sentence responsibility (M4 flagged a first wording with an "and"; rewritten). No behaviour
is added, so there is nothing yet for a test to fail on; D2's oracle is written first in the next
pull request.


Review budget

docs/os/05-workflow.md §4

  • Lines changed (excluding generated): ~330, almost all the ADR and AGENTS.md
  • Files touched: 8 (5 of them scaffolding)
  • Within budget
  • ⚠️ Over budget — label required, justification:

Contracts

  • No contract affected
  • Contract consumed — the version is declared in the manifest

Not verified

  • nstack doctor exits 1 with 0 gaps and 13 not verified — the GitHub-side settings it cannot
    read from this sandbox, as on previous pull requests.
  • That the venue's API page accepts a name carrying valid_until: an assumption in the ADR, to be
    observed on D2's test sheet.

🤖 Generated with Claude Code

…n take back

The module is scaffolded as `critical` and `user_facing` — cycle 03 says it is
created when the cycle is accepted, and it was, today. It holds its description
only: no code, no commands yet, so its first pull request with code declares
`check` and `test`.

ADR-0001 is proposed with it, because creating a module is a decision and this
one's decision is where the money is. flet generates one agent key per member
and never touches the main key: the member approves the agent on the venue's own
API page, named `flet valid_until <30 days>`. There is no revoke action on the
venue; an agent dies by expiry or by being replaced under its name, so
revocation is the member's act on the venue and flet reads `extraAgents` before
every action, doing nothing when its agent is absent or expired. A fresh address
every time, because a deregistered agent's nonces may be pruned and its old
signatures replayed. At rest, Fernet under a secret from the environment, mode
0600 — which protects a leaked file or backup and says plainly it does not
protect a compromised server.

The decider chose on 2026-09-24: the venue's page rather than a signing page of
ours, 30-day expiry, and testnet with a wallet they fund.

What the venue does not document is written as such: the unit of `valid_until`,
`extraAgents` itself (SDK only), and the list of what an agent may sign. D2's
tests establish those by asking the venue.

`nstack fitness` compliant.

Agent-Session: 98242fbe-7c26-467e-a3e9-e8816ec93493
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@napkinstack-agent
napkinstack-agent Bot merged commit 3aa17f8 into main Sep 24, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant