Skip to content

docs(ams): document AMS's verified standalone, ORB/gittensor-optional capability #6842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JSONbored merged 1 commit into from
Jul 17, 2026
Merged

docs(ams): document AMS's verified standalone, ORB/gittensor-optional capability #6842

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions apps/loopover-ui/content/docs/ams-deployment.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,6 +237,18 @@ sends SIGTERM, which the loop handles cleanly at its next kill-switch check.
- Discovery/ranking primitives that touch GitHub only run when explicitly invoked and only perform
documented GETs unless a future command says otherwise.
- Operators own secret injection; images and packages ship without embedded tokens.
- AMS works against **any** GitHub repository — it does not require ORB installed, gittensor
registration, or a `.loopover.yml` file on the target repo to function.

<Callout variant="note" title="Verified against a real, non-gittensor repo">
`loopover-miner init`, `doctor`, and `discover <owner/repo>` were run end to end against real
public GitHub repositories with no `.loopover.yml` and no gittensor registration, using only a
plain `GITHUB_TOKEN` — every step worked as documented, including correctly returning zero
candidates on a repo with no open issues and ranking real issues on repos that had them. The
`loopover-mcp login` device-flow session path (a separate mechanism from AMS's own credential
resolution) currently has a known reliability issue independent of AMS itself — see the linked
issue tracker for status before relying on it for unattended AMS setups.
</Callout>

For operational scenarios (ledger corruption, two miners on one state dir, post-upgrade schema
migration) see the [AMS operations runbook](/docs/ams-operations-runbook), and for measured
Expand Down
1 change: 1 addition & 0 deletions packages/loopover-miner/DEPLOYMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,6 +180,7 @@ Want the dashboard too? [`systemd/loopover-miner-ui.service.example`](../../syst
- `loopover-miner status` and `loopover-miner doctor` make **no network calls**.
- Discovery/ranking primitives that touch GitHub only run when explicitly invoked and only perform documented GETs unless a future command says otherwise.
- Operators own secret injection; images and packages ship without embedded tokens.
- AMS works against **any** GitHub repository — it does not require ORB installed, gittensor registration, or a `.loopover.yml` file on the target repo to function. Verified end to end (`init`, `doctor`, `discover <owner/repo>`) against real public repositories with no `.loopover.yml` and no gittensor registration, using only a plain `GITHUB_TOKEN`.

See [`docs/operations-runbook.md`](docs/operations-runbook.md) for operational scenarios: ledger corruption, two miners on one state dir, and post-upgrade schema migration ([#4875](https://github.com/JSONbored/gittensory/issues/4875)).

Expand Down
Loading