@rahmantech/knl-view 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Muhammad Abdurrahman
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,399 @@
-# Temporary Holding Version
+# knl-view
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+A local viewer for `.knowledges` knowledge bases: a CLI that serves a small web
+app over a plain folder of Markdown files. The disk is the source of truth;
+`map.json` is optional decoration.
+
+```
+knl-view --port 8086 --path=.knowledges
+```
+
+## What it does
+
+- Serves a web viewer over any folder of Markdown files. No database, no build
+  step for your content, no account.
+- Sidebar tree with a fixed `index` entry (the root `README.md`) and a
+  `contents` entry that lists the whole base on one page.
+- Folders open their own `README.md`, rendered the same way as a normal document.
+- `map.json` (optional) relabels, reorders, or hides entries in the menu. It
+  never creates, moves, or deletes files. Entries pointing at paths that are not
+  on disk are ignored silently.
+- Markdown with GFM tables, and triple-backtick fences tagged `mermaid` rendered
+  as diagrams. The mermaid bundle is served locally and loaded only when a
+  document contains a diagram; nothing is fetched from a CDN.
+- Per-diagram controls: toggle between diagram and source, and a zoom modal
+  (wheel zoom, drag to pan, +/−/Reset, Esc to close).
+- Table of contents per document, breadcrumb, and a filter box in the sidebar
+  that narrows the index by file title or path.
+- Interface in English or Indonesian, switchable in the top bar. English is the
+  default.
+
+## Requirements
+
+- Node.js 20.19 or newer.
+- A built frontend. `dist/` is committed to this repository, so an install from
+  GitHub already has it. The CLI refuses to start without it and tells you so.
+
+## Install
+
+```sh
+npm install -g @rahmantech/knl-view
+```
+
+That puts the `knl-view` command into Node's global bin,
+`$(npm prefix -g)/bin`. If that directory is not on your PATH, link the
+command somewhere that is:
+
+```sh
+ln -s "$(npm prefix -g)/bin/knl-view" ~/.local/bin/knl-view
+```
+
+The published tarball ships the built `dist/`, so the install compiles
+nothing.
+
+Run it once without installing:
+
+```sh
+npx @rahmantech/knl-view
+```
+
+Or install from source, for a local checkout or an unreleased commit:
+
+```sh
+git clone https://github.com/rachmanzz/knl-view.git
+cd knl-view
+npm install
+npm run build
+npm link
+```
+
+`npm link` puts `knl-view` on your PATH from the checkout. To install a
+GitHub commit without cloning, run
+`npm install -g github:rachmanzz/knl-view --install-links`; without
+`--install-links`, npm 11 links against a temporary clone it deletes
+afterwards, which leaves a broken install.
+
+## Usage
+
+```sh
+knl-view                                   # serve ./.knowledges on 127.0.0.1:8085
+knl-view --path=../other-project/.knowledges
+knl-view --port 8086 --host 0.0.0.0        # expose on the network
+knl-view graph trace --target=README.md    # query on-demand subgraph for AI
+knl-view graph trace --target=DEC-20261030-135001 --hops=1
+knl-view --init                            # scaffold a new base (wizard, no server)
+knl-view --seed-skill=knl-view --dir=global --yes
+```
+
+| Flag | Default | What it does |
+| --- | --- | --- |
+| `--port`, `-p` | `8085` | HTTP port |
+| `--path` | `.knowledges` | Folder to serve, relative to the working directory |
+| `--host` | `127.0.0.1` | Bind address |
+| `--anchordb` | none | AnchorWire URL (`wire://host:port?token=...`) for this session; overrides the global config block |
+| `--target` | none | Target node ID for CLI subgraph trace (`knl-view graph trace`) |
+| `--hops` | `2` | Traversal depth radius for subgraph extraction |
+| `--init` | off | Scaffold a new base interactively; does not start the server |
+| `--structure` | `standard` | Layout for a non-interactive `--init`: `standard`, `empty`, or `custom` |
+| `--folders` | none | Comma-separated folder names for `--structure=custom` |
+| `--seed-skill=knl-view` | off | Write the `knl-view` skill for coding agents; skipped if it already exists |
+| `--dir` | `project` | Skill location: `project` (`.agents/skills`) or `global` (`~/.config/opencode/skills`) |
+| `--yes`, `-y` | off | Accept every default in `--init` / `--seed-skill`, no questions asked |
+| `--help`, `-h` | | Show help |
+| `--version`, `-v` | | Show version |
+
+The server binds to `127.0.0.1` by default, so it is reachable only from your
+machine unless you pass `--host` yourself. There is no authentication; treat
+`--host 0.0.0.0` as a decision you are making on purpose.
+
+## Configuration
+
+Two optional config files. A missing file is never an error; a broken file is
+ignored with one warning on stderr. CLI flags always win over config values.
+
+**Global (`~/.knlview/knl-config.json`)**: shared by every project on the
+machine. Holds the `anchordb` block. Without it, AnchorDB stays completely
+off and the viewer runs fully local:
+
+```json
+{
+  "anchordb": {
+    "url": "wire://127.0.0.1:7448",
+    "token": "your-token",
+    "sync": true
+  }
+}
+```
+
+**Per project: `knl-config.json` at the project root** (gitignored): only
+`path`, `port`, `host`, and a `models` map, never the anchordb connection:
+
+```json
+{
+  "port": 8091,
+  "models": {
+    "knowledges": "vez0vqrp",
+    "consensus": "n0qrnmsz"
+  }
+}
+```
+
+Model names are owned by the `models` map: role → name, and the name can
+be anything (random names are fine; the map records what each name is
+*for*). Names stay stable even if the project folder is renamed. knl-view
+never invents names by itself: create them with
+`knl-view model new <role>` (writes the map and the global registry), and
+inspect ownership with `knl-view model check`.
+
+The global registry `~/.knlview/models.json` records every name's owner
+(project, role, path) and warns when two projects claim the same name. A
+project whose map has no entry for a role runs fully local: AnchorDB is
+touched only once the role is mapped.
+
+## Installing AnchorDB (optional)
+
+AnchorDB is an optional layer. Without it the viewer runs fully local:
+everything (browsing, search, the graph engine, and `knl-view graph trace`)
+works with zero setup. Installing AnchorDB only adds persistent causal
+tracing across sessions and shared sync between machines.
+
+`knl-view install anchordb` installs AnchorDB and writes the `anchordb`
+block into the global config:
+
+- **Linux and macOS**: downloads the native binary from
+  [GitHub Releases](https://github.com/rachmanzz/anchordb/releases),
+  verifies it against the release's `SHA256SUMS.txt`, installs to
+  `~/.knlview/bin/`, and starts `anchordb-server` detached (logs in
+  `~/.knlview/anchordb.log`, data in `~/.knlview/anchordb-data`).
+- **Other platforms**: a Linux container from
+  `ghcr.io/rachmanzz/anchordb` via docker or podman; the command refuses
+  to continue if neither is installed.
+
+Non-interactive (CI/scripts): add `--yes`. Explicit method: `--method=binary`
+or `--method=container`. Fixed token instead of a random one: `--token=...`.
+If a container named `anchordb-knlview` already exists, the installer stops
+instead of removing it: data must not disappear by accident.
+
+## How a base is read
+
+A base is an ordinary folder:
+
+```
+.knowledges/
+  README.md          # the index document
+  map.json           # optional
+  roadmap/
+    README.md
+    q1.md
+  features/
+    auth.md
+```
+
+Reading order: the root `README.md`, then `map.json` when present, then the
+structure on disk. Without `map.json`, menu labels fall back to the first
+`# heading` of each file, then to the plain file name (files before folders).
+
+### map.json
+
+Every entry is decoration. Nothing in it can invent a file that is not on disk.
+
+```json
+{
+  "title": "Base title shown in the masthead",
+  "sections": {
+    "roadmap": { "title": "Roadmap", "order": 1, "meta": "Where this is going" }
+  },
+  "docs": {
+    "coding-rules.md": { "title": "Coding rules", "order": 1 }
+  },
+  "files": {
+    "rahasia.md": { "ignore": true }
+  },
+  "dirs": {
+    "draft-lama": { "ignore": true }
+  }
+}
+```
+
+| Field | Applies to | Effect |
+| --- | --- | --- |
+| `title` | the whole file | Masthead title; wins over the README heading |
+| `sections.<dir>` / `dirs.<path>` | a directory | `title` is the menu label, `meta` is a short note |
+| `docs.<file>` / `files.<path>` | a file | `title` is the menu label |
+| `order` | any entry | Ascending menu order; entries without `order` follow, files before folders |
+| `ignore` (or `hidden`) | any entry | `true` hides it from the menu, lists, search, home, and contents |
+
+Paths are relative to the `.knowledges` root, use `/` separators, and must
+match the on-disk path exactly, for example `features/auth.md`. `ignore` is
+view-only: the file stays on disk. Remove the flag to bring it back.
+
+The full field reference lives in the bundled skill:
+`.agents/skills/knl-view/SKILL.md`.
+
+## AI Graph & Decision Tracing
+
+`knl-view` includes an AI-native directed acyclic graph (DAG) engine built directly into the CLI and server. It connects knowledge documents (`.knowledges/*.md`) and architectural decision records (`.knowledges/decisions/*.md`) into a unified graph:
+
+- **Zero Intermediary File**: Fully on-the-fly in-memory processing. Markdown files remain the sole source of truth without generating out-of-sync `graph.json` cache files.
+- **Decision Lineage Tracking**: Automatically discovers `supersedes`, `related_to`, and `affects_knowledge` edges from `decisionskills` decision blocks.
+- **Low-Token Subgraphs for AI**: Instead of loading an entire knowledge base into LLM context, query exact $N$-hop subgraphs in sub-milliseconds (< 1 ms).
+
+This engine is fully local: it needs no AnchorDB and no network. AnchorDB
+(see the optional install above) adds persistence on top: edges survive
+across sessions, are synced incrementally, and can be traced from any
+machine pointing at the same server.
+
+### Two-way lineage
+
+Traces walk in a mechanically defined direction relative to the edges,
+never interpreted as cause and effect (`depends_on` edges *leave* a
+decision while pointing at its upstream, so up/down labels would lie):
+
+- `direction=out`: edges leaving the target: what it supersedes,
+  `depends_on`, or affects.
+- `direction=in`: edges entering the target: what references or
+  replaces it.
+- `direction=both`: the default for the local graph trace; the full
+  neighborhood.
+
+Every returned node carries `via` (`center`, `in`, `out`, or `in+out`)
+telling how it connects to the trace center.
+
+CLI: `knl-view graph trace --target=<id> --direction=out`
+HTTP: `GET /api/graph/trace?target=<id>&direction=in`
+
+The AnchorDB endpoint adds the same parameter,
+`GET /api/anchordb/trace?target=<id>&direction=in|out|both` (default
+`out`): `out` is scored server-side via `causalChain`; `in` is walked
+backwards from the local sync mirror; the wire protocol has no reverse
+query, and the mirror holds every edge this project ever linked, so it
+is exactly the inbound map for this project's model. Mirror results
+carry score 1 and the response reports `mirrored: true`/`false` so
+consumers know which half came from where.
+
+### Consensus (claims)
+
+A second AnchorDB model, the `consensus` role in the project's models map,
+holds agreement and conflict between *claims*: short statements that are
+content-addressed (`c-` + 16 hex chars of the statement's hash), so the same
+text is the same claim on every machine. Claims relate only to other claims,
+through two fixed relation types: `agrees_with` and `contradicts`. The
+consensus structure lives purely in AnchorDB; the local artifacts (claim
+index in `~/.knlview/claims/`, edge mirror in `~/.knlview/sync-state/`) are
+caches that degrade convenience, never the data.
+
+A claim's status is derived from who points at it: any incoming `contradicts`
+makes it `disputed`, otherwise any incoming `agrees_with` makes it
+`consensus`, otherwise it is `uncontested`.
+
+```sh
+knl-view consensus claim "We use bcrypt for password hashing"
+knl-view consensus agree c-a1b2c3d4e5f6a1b2 c-437ff9f10f83edde
+knl-view consensus contradict c-a1b2c3d4e5f6a1b2 c-437ff9f10f83edde
+knl-view consensus retract c-a1b2c3d4e5f6a1b2 c-437ff9f10f83edde
+knl-view consensus status c-437ff9f10f83edde
+knl-view consensus list
+```
+
+Mutations are CLI-only on purpose: one write path, one mirror kept honest.
+The read-only HTTP endpoint answers "is this claim settled?":
+
+`GET /api/consensus?target=<claimId>` returns the claim's `status`,
+`supporters`, `objectors`, its own `stance`, `mirrored` (whether a valid
+local mirror backs the inbound half), and a `statements` map of the
+claim texts involved. Returns `503` when AnchorDB is off or the
+`consensus` role is not mapped.
+
+### Sources graph (whole project)
+
+A third AnchorDB model, the `sources` role in the models map, holds the
+dependency graph of the whole project, not just `.knowledges`. Every file
+becomes a node (id = repo-relative path; hidden folders are skipped except
+`.github`, and `node_modules`, `dist`, and `.gitignore` patterns are
+ignored). Import edges are extracted with tree-sitter syntax parsing (the
+JS family and Go today, one grammar package per language) and stored in
+both directions (`imports`, `imported_by`) so lineage works without any
+local mirror: sync is server-authoritative, enumerating the server's own
+records and edges before applying the difference from a fresh disk scan.
+
+Each file also defines **symbol nodes**, extracted from the same parse:
+
+- Symbol ids are `<path>#<name>`; class methods are `Class.method`. A name
+  defined more than once in one file gets a line suffix
+  (`<path>#<name>@<line>`), so duplicate helpers stay distinct records.
+- Kinds: `function`, `class`, `method`, `type` (Go type declarations).
+- Edges: `defines`/`defined_in` (file → symbol) and `calls`/`called_by`
+  (symbol → symbol), each stored in both directions because causalChain
+  walks forward only.
+- Call resolution is conservative: a call belongs to its innermost
+  enclosing symbol, and the callee must match exactly one definition
+  project-wide (same package directory preferred in Go). A receiver-qualified
+  call (`obj.Method()`) resolves only when the receiver is an import
+  binding of the file, otherwise it is skipped, never guessed.
+- Label text (symbol names and kinds; AnchorDB attributes are
+  numeric-only) is written to `.knowledges/.knl-data/<path>.md`, one file
+  per source file that has symbols; override the location with `labelDir`
+  in the project config. Labels are regenerated and pruned on every sync.
+
+```sh
+knl-view model new sources
+knl-view sources sync
+knl-view sources collect
+knl-view sources trace --target=server/index.js --direction=out --hops=2
+knl-view sources trace --target=server/index.js#handleTrace --direction=in
+```
+
+`sync` is idempotent: run it again after refactoring and only the
+difference is applied. A target containing `#` traces symbol lineage over
+`calls`/`called_by`; a plain path traces file lineage over
+`imports`/`imported_by`. Records the disk no longer has are archived with
+the native lifecycle opcode 2 (TOMBSTONE: the server hides them from list
+and lookups) after their edges are unlinked, and the `tombstone = 2`
+attribute stays as a marker for servers that predate opcode support.
+`sync` then asks the REST collector to purge those records physically
+(scoped to the model); run `knl-view sources collect` by hand if the REST
+endpoint was unreachable at that moment. A reappearing file revives the
+record with a normal save and relinks its edges. Sync reports
+`ORPHAN EDGES` when an edge endpoint failed to save, so a broken sync is
+never silent. The read-only HTTP endpoint answers the same queries:
+`GET /api/sources/trace?target=<id>&direction=in|out|both&hops=N`.
+
+### CLI Query
+
+```sh
+knl-view graph trace --target=DEC-20261030-135001 --hops=1
+```
+
+Outputs a compact JSON subgraph to `stdout` containing the focal node and all direct dependencies/impacted components.
+
+### HTTP Endpoints
+
+When `knl-view` is running as a local server:
+- `GET /api/graph`: Returns the entire knowledge and decision graph structure.
+- `GET /api/graph/trace?target=<id>&hops=2`: Returns an isolated $N$-hop neighborhood subgraph for AI agents or interactive visualization.
+- `GET /api/anchordb/trace?target=<id>&hops=2`: Returns a causal chain traced on the AnchorDB server (requires the global `anchordb` config block). Returns `503` when AnchorDB is off or unreachable.
+- `GET /api/consensus?target=<claimId>`: Read-only consensus status for one claim (requires AnchorDB and a mapped `consensus` role). Returns `503` when AnchorDB is off or the role is unmapped, `400` without a target.
+- `GET /api/sources/trace?target=<path>&direction=in|out&hops=2`: Read-only file lineage over the whole-project sources graph (requires AnchorDB and a mapped `sources` role). Returns `503` when unavailable, `400` without a target or with a bad direction.
+
+## Development
+
+```sh
+npm run dev
+```
+
+Starts the API on port 8085 (override with `PORT`) and the Vite dev server on
+5173 (override with `WEB_PORT`). Pass a base folder as the first argument:
+
+```sh
+npm run dev -- ../some-project/.knowledges
+```
+
+`dist/` is committed to this repository so that installs straight from GitHub
+keep working, because npm runs no build step for a git install without a
+`prepare` script. After changing the frontend, run `npm run build` and commit
+the result together with the source, or those installs stay on the previous
+build.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).