factcircuit
FactCircuit: an auditable claim-and-evidence verification loop with immutable provenance, staged checks, bounded retrieval, and reproducible evaluation.
Anaphora harvests screenshots and raw data from Kibana, Grafana, Metabase and any web app, lets an AI read the dashboards visually and reason across sources, and alerts a human only when it matters. B
DataCSS · TypeScriptGitHub @beshu-techOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Documentation for Anaphora - Automated Kibana, Grafana Reports & Alerts
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗This website is built using Docusaurus, a modern static website generator.
yarn
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
yarn build
This command generates static content into the build directory and can be served using any static contents hosting
service.
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the
gh-pages branch.
develop branch creates a new patch release. The version number is automatically incremented.preview-0.9.1.Unreleased section of the CHANGELOG. If no Unreleased section
exists, create one at the top of the changelog.develop into main.0.9.0 and latest.Unreleased section to the new version and date, and add any additional changes
that were not included in patch releases.To create a new stable documentation version, run npm run update-stable-version. This will:
docs/ content available under versioned_docs/version-stable/docs/ directory will be available in the main documentation now.