cyph3rasi
12c806c77f
Hop-State: A_06FN8NFDRFAFN5VCJTHJAAG Hop-Proposal: R_06FN8NEGJ054CPMJF9ZAN70 Hop-Task: T_06FN8HT6XG332C3XY6PYCCG Hop-Attempt: AT_06FN8HT6XGRXW0B4WPFFBJG
65 lines
2.5 KiB
Markdown
65 lines
2.5 KiB
Markdown
# HopWeb
|
|
|
|
HopWeb is a collaborative forge for prompt-native software development.
|
|
|
|
It uses Git for durable source storage and Gitea for the proven forge substrate,
|
|
but makes Hop's workflow the primary product model:
|
|
|
|
- a **task** captures the outcome someone wants;
|
|
- a **prompt state** records each instruction in its causal context;
|
|
- an **attempt** is an isolated line of human or agent work;
|
|
- a **checkpoint** freezes the exact tree that was evaluated;
|
|
- **evidence** records checks against that immutable checkpoint;
|
|
- a **proposal** is a reviewable candidate outcome; and
|
|
- an **accepted state** is the current shared truth.
|
|
|
|
The repository **Prompts** view is a private, per-user review surface for that
|
|
causal record. The control plane identifies the signed-in Gitea user and only
|
|
returns prompt rows attributed to that user's immutable Gitea ID.
|
|
|
|
Hop's local state and exported prompt records can contain private requests and
|
|
machine paths, so `.hop/` is ignored and must never be published through Git.
|
|
`make hop-records` may be used for a local export, but its output remains local.
|
|
|
|
The product thesis is simple:
|
|
|
|
> GitHub organizes collaboration around commits and pull requests. HopWeb
|
|
> organizes human-agent collaboration around intent, attempts, evidence, and
|
|
> accepted outcomes.
|
|
|
|
## Foundation
|
|
|
|
Gitea supplies the expensive, mature infrastructure we should not rebuild:
|
|
|
|
- Git transport, repositories, LFS, and permissions
|
|
- users, organizations, teams, OAuth, and access tokens
|
|
- issues, notifications, webhooks, releases, packages, and Actions
|
|
- administration, audit surfaces, and deployment primitives
|
|
|
|
Hop supplies the differentiating control plane and experience:
|
|
|
|
- prompt and state graph persistence
|
|
- task and attempt orchestration
|
|
- agent identity and attribution
|
|
- checkpoint-bound validation evidence
|
|
- proposal review and acceptance semantics
|
|
- a Hop-native repository, task, attempt, and review interface
|
|
|
|
See [the product blueprint](docs/product-blueprint.md) and
|
|
[the Gitea foundation decision](docs/adr/0001-gitea-as-forge-foundation.md).
|
|
|
|
## First release
|
|
|
|
The first useful release is not a complete GitHub clone. It is a private,
|
|
single-installation forge where a user can:
|
|
|
|
1. create or import a repository;
|
|
2. open a task with a prompt;
|
|
3. launch one or more isolated agent attempts;
|
|
4. watch states, diffs, and checks appear live;
|
|
5. compare proposals by outcome and evidence; and
|
|
6. accept one proposal into the repository's shared state.
|
|
|
|
Everything else should be inherited from Gitea until the Hop workflow proves
|
|
that it needs a different abstraction.
|