3.3 KiB
3.3 KiB
Wiki Schema
Domain
Yuta の関心に基づく、技術・公共性・知識管理の個人 Wiki。
中心に置く領域:
- LLM、AI エージェント、自動化、開発者向けの道具
- LLM Wiki、Obsidian、Scrapbox、howm などの知識管理と記録の仕組み
- 品質保証、検証、セキュリティ、供給網、信頼できる運用
- デザイン、ハック、Hacker News 的なニッチでわくわくする技術や発想
- 公共のための技術、行政・市民向けの仕組み、アクセシビリティ
- 報道、偽情報、SNS 上の情報操作、情報基盤の責任
この Wiki は「LLM Wiki についての Wiki」だけではない。LLM Wiki は運用方法の一部であり、各トピックは無理に LLM Wiki と接続しなくてよい。資料そのものが持つ公共性、設計、実装、社会的意味を優先して整理する。
Conventions
- File names: lowercase, hyphens, no spaces (e.g.,
llm-wiki-pattern.md) - Every wiki page starts with YAML frontmatter.
- Use Obsidian-style double-bracket links between pages; aim for at least 2 outbound links per page.
- When updating a page, always bump the
updateddate. - Every new page must be added to
index.mdunder the correct section. - Every action must be appended to
log.md. - Raw sources under
raw/are immutable after ingest.
Frontmatter
---
title: Page Title
created: YYYY-MM-DD
updated: YYYY-MM-DD
type: entity | concept | comparison | query | summary
tags: [from taxonomy below]
sources: [raw/articles/source-name.md]
confidence: high | medium | low
---
raw/ Frontmatter
---
source_url: https://example.com/article
ingested: YYYY-MM-DD
sha256: <hex digest of raw body>
---
Tag Taxonomy
- AI and automation: llm, agent, automation, evaluation
- Knowledge systems: wiki, knowledge-base, retrieval, synthesis, maintenance, obsidian, markdown
- Development practice: dev-tool, cli, git, workflow, quality, security, supply-chain, reliability, data-format
- Design and hacks: design, hack, interface, hn-like
- Public interest: public-interest, civic-tech, accessibility, inclusive-design, media, disinformation, information-integrity, data-protection, privacy, freedom-expression, law
- Entities and roles: person, organization, tool, human-in-the-loop
- Meta: comparison, source
Page Thresholds
- Create a page when an entity/concept is central to one high-signal source, appears in 2+ sources, or clearly fits the domain interests above.
- Prefer creating/updating pages for durable ideas, tools, people, organizations, practices, and public-interest issues that are likely to be useful later.
- Keep one-off news, shallow product announcements, ads, campaigns, and low-context links in raw only or skip them.
- Do not force pages to connect to LLM Wiki. Use the natural frame: design, public interest, accessibility, security, information integrity, automation, etc.
- Add to an existing page when a source concretely extends what is already covered.
- Do not create pages for passing mentions.
- Split a page when it exceeds ~200 lines.
Update Policy
When new information conflicts with existing content:
- Check source dates.
- Note both positions with dates and sources.
- Mark contested pages with
contested: trueand/orcontradictions:. - Flag for user review in lint output.