standmeet/sijie·wiki
writingchat
wiki tree
loading…
624 entries · 12 roots · 157 gated
tracking consentThis site keeps an anonymous, cookieless count of visits so the owner can see what people read — no personal data is stored. May we count this one?
← wiki▸access-control
2026-09-23·by Sijie Wang

access-control

read next
  • access-control-diagram-coverage →
  • acl-and-quota-granularity →
  • byoai-browser-vault →
  • byoai-envelope →
  • coded-landing-and-code-rotation →
  • owner-keypair-auth →
  • owner-sessions-and-abuse-controls →
  • role-snapshot-frozen →
  • trusted-identity-via-meta →
cited by
  • access-control-diagram-coverage →
  • acl-and-quota-granularity →
  • architecture →
  • byoai-browser-vault →
  • byoai-envelope →
  • coded-landing-and-code-rotation →
  • owner-keypair-auth →
  • owner-sessions-and-abuse-controls →
  • requirements-to-design →
  • role-snapshot-frozen →
  • trusted-identity-via-meta →
about this entry

One of sijie's wiki entries. The AI on this site is grounded in the same corpus and answers in sijie's voice, with citations back to entries like this one — answering costs sijie money, so it waits behind a code: enter an access code →

ask about this

Ask this entry a question.

The AI answers in the owner’s voice, grounded in this corpus. Bring your own key and start — it never leaves your browser.

no code?·BYOAI

Bring your own AI.

Use your own key against the owner’s public corpus. Pick any OpenAI-compatible provider, or point at your own self-hosted endpoint. Private topics return “need a code”.

  • · your key never touches our server — stored encrypted in your browser only
  • · owner pays for retrieval, you pay for inference
  • · private topics return “ask for a code”
choose a model
endpoint
model
api keynever uploaded · stored encrypted in your browser
fill endpoint, model + key to unlock the public chat.