Loading…
OKF Documents
Loading configured document roots…
Prototype graph view: documents are nodes, internal Markdown references are edges, and frontmatter topics can be shown as semantic hubs.
OKF AI analysis
Run explicit Voyage analysis, review AI-suggested edges, and persist every decision in the local OKF SQLite index.
Editor access
Reading remains anonymous. Protected actions require either the one-time local-editor code or an HTTPS account with the corresponding role.
- Documents
- 0
- Graph edges
- 0
- Suggested edges
- 0
- Accepted
- 0
Ready. No analysis has been run in this browser session.
Semantic search and evaluation
Suggested graph edges
Voyage-derived suggestions and review decisions are durable SQLite state. Local metadata prefilters are shown separately and cannot be accepted.
No suggestions yet.
Durable storage path
SQLite is the durable review source consumed by the explicit relation-application endpoint. Export is an optional portable review artifact, not hidden browser state.
No accepted changes saved yet.
Document root management is protected
Reading remains available without signing in. Authenticate or pair this browser before viewing or changing document-root configuration.
Add an OKF document root
Enter a server-side directory. OKF never provides a general filesystem browser and never admits hidden or unsupported files.
Pair or sign in, then create a preview.
Review current proposal
| Path | Admission | Reason | Resource type |
|---|
Initialization is a separate source-writing operation. You will see every proposed file change and must confirm it again.
Browser configuration
This list comes from ~/.config/okf/config.toml. Browser changes never edit .env.
Configuration is available after pairing or sign-in.
Detected root changes
Detection is read-only and token-free. Nothing below changes configuration, source files, relations, embeddings, Voyage state, or the accepted baseline.
| Path | Current state | Reason |
|---|
Dismissal does not approve files or move the baseline. The same changes can appear again after the next explicit check or server start.