+
+
+
The prompt-native forge
+
Turn a clear outcome into accepted, verified work.
+
Hop gives people and AI agents one shared workflow for building software: state the goal, run isolated attempts, review the evidence, and accept the result.
+
+
+
+

+
Outcome ready for review
+
+
+
+
+ A better unit of collaboration
+ Software work begins with intent, not a branch.
+ Git remains the durable home for your files. Hop makes the work around those files legible: what was asked for, who attempted it, what was checked, and which outcome became shared truth.
+
+
+
+
+ 01
+ Keep the why attached
+ Each task starts with the requested outcome and retains its causal context, so nobody has to reconstruct intent from a terminal history.
+
+
+ 02
+ Try work without collisions
+ Human and agent attempts run in isolated workspaces. Compare different approaches without putting your main line at risk.
+
+
+ 03
+ Review proof, not promises
+ Checks are bound to immutable checkpoints, making it clear exactly what was verified before a proposal is accepted.
+
+
+
+
+
+
How Hop works
+
A calm, visible path from request to shared truth.
+
+
+ - 1
Open a task
Describe the outcome you need in plain language.
+ - 2
Launch an attempt
Work yourself, direct an agent, or run both approaches side by side.
+ - 3
Inspect the evidence
Review diffs, checkpoints, and the checks attached to them.
+ - 4
Accept the outcome
Choose the verified proposal that should become the shared state.
+
+
+
+
+
+{{template "base/footer" .}}
diff --git a/docs/gitea-hop-native.md b/docs/gitea-hop-native.md
index 3f6a646..295dcc5 100644
--- a/docs/gitea-hop-native.md
+++ b/docs/gitea-hop-native.md
@@ -1,8 +1,7 @@
# Hop-native Gitea semantics
-HopWeb keeps Gitea's existing interface design and changes the meaning of its
-collaboration elements. No custom stylesheet, theme, component library, or
-layout override is installed.
+HopWeb keeps Gitea's existing forge interface and adds a Hop-specific public
+home page, brand mark, and semantic vocabulary for collaboration elements.
## Install
@@ -18,9 +17,10 @@ Set `ENV_FILE` when the Compose environment is stored elsewhere:
ENV_FILE=/path/to/environment ./deploy/gitea/install-hop-native.sh
```
-The installer copies the adapter into Gitea's persistent custom directory,
-sets the application name to `Hop`, restarts Gitea, and waits for a healthy
-response. Re-run it after editing the adapter or replacing the Gitea volume.
+The installer copies the home page, brand mark, styles, and adapter into
+Gitea's persistent custom directory, sets the application name to `Hop`,
+restarts Gitea, and waits for a healthy response. Re-run it after editing an
+asset or replacing the Gitea volume.
## Semantic mapping
@@ -52,4 +52,3 @@ After changing the pinned Gitea version:
4. confirm proposal creation and acceptance labels;
5. inspect browser console errors; and
6. test a narrow viewport and keyboard navigation.
-