Skip to content

[DEV] Tell the harness agent not to extend a non-deployable contract - #143

Merged
shellygr merged 2 commits into
devfrom
shelly/dev-pr-130
Aug 10, 2026
Merged

[DEV] Tell the harness agent not to extend a non-deployable contract#143
shellygr merged 2 commits into
devfrom
shelly/dev-pr-130

Conversation

@shellygr

@shellygr shellygr commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Mirror of #130 onto the dev bleeding-edge branch.

Source branch: shelly/harness-prompt-abstract-targets. This branch is that head merged forward with dev; #130 itself is untouched and still targets master.

Per the dev branch policy this merges without review once pyright and pytest are green.

shellygr and others added 2 commits August 7, 2026 21:18
The instruction to write "a minimal contract which simply extends the target"
holds only when the target is deployable. Extending an abstract contract --
or one that leaves part of an inherited interface to a sibling that is mixed
in further down the hierarchy -- produces a harness solc rejects, and even if
it compiled the Prover would have no instance for it. Judging deployability
also cannot be done from the target's own file: the unimplemented functions
may be declared in an interface it inherits.

Direct the agent to harness the concrete contract the protocol deploys in
that case, and to fill in the missing functions itself only when the project
has no concrete contract inheriting from the target.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@shellygr
shellygr merged commit 955e6d1 into dev Aug 10, 2026
2 checks passed
@shellygr
shellygr deleted the shelly/dev-pr-130 branch August 10, 2026 11:35
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