# avokb — Knowledge Base Bootstrap

This is a user-owned filesystem knowledge base. Plain files, no database,
no proprietary format. Every access path below is a view onto the same
canonical directory.

## Permission

Do not initiate authentication or request access unless the user has
explicitly authorized access to this knowledge base.

Never ask the user to paste private keys, passwords, OAuth tokens, or
other credentials into ordinary chat.

## Requesting access

If you have no access yet, ask for it — do not attempt to guess or reuse
credentials.

**For SSH**, the user cannot give you a key; you make your own and they
install the public half:

1. Generate a key pair on the machine you actually run on, dedicated to
   this knowledge base:
   `ssh-keygen -t ed25519 -C "<who-and-where-you-are>" -f ~/.ssh/avokb -N ""`
2. Send the user the contents of the **`.pub`** file only — that half is
   safe to paste anywhere. The private half never leaves your machine and
   must never be sent, printed, or copied into chat.
3. Ask them to install it. Access takes effect immediately; nothing needs
   restarting.
4. Connect with `-i` pointing at your private key.

**For MCP**, complete the OAuth flow yourself in the ordinary way. The
user holds the password and enters it themselves — do not ask for it.

One key per machine, so a lost or retired one can be revoked on its own.
If you no longer need access, say so and ask the user to remove your key.

## MCP

Endpoint: `https://avokb-mcp.azamrahman.com/mcp`

Provides read and write access to the knowledge-base filesystem,
authenticated via OAuth. If access is not already authorized, ask the
user for permission and let them complete authentication themselves.

## SSH

    ssh -p 2222 avokb@avokb.azamrahman.com

Key-only; there is no password. The shell is confined to a container that
can see the knowledge base and nothing else on the host. If SSH access has
not been provisioned, ask the user before attempting to establish it.

## Web

`https://avokb.azamrahman.com` — browse, edit, and upload through
FileBrowser. Human-facing; agents should prefer MCP or SSH.

## Layout

The knowledge base root contains:

    README.md        what this KB is and how it is organised
    AGENTS.md        conventions agents should follow when writing here
    inbox/           unsorted; triage from here
    projects/        one directory per project
    knowledge/       durable reference material
    datasets/        structured data
    scripts/         utilities that operate on this KB
    attachments/     binaries referenced from notes

## After access

Read `README.md` and `AGENTS.md` at the KB root before modifying anything.