Skip to content

appleweiping/WEIPING_WIKI

Repository files navigation

Weiping Wiki

WEIPING_WIKI

A source-backed knowledge system for turning research, conversations, and agent work into maintained, interlinked Markdown.

Current public identity: WEIPING_WIKI / Weiping Wiki.

Historical aliases preserved for compatibility: vipin wiki, vipinknowledge, and vipin-wiki. Older paths, slugs, prompts, and automation snippets may still mention those names until they are safely migrated; treat them as aliases, not the current project identity.

The wiki is the public crystallization layer. Day-to-day agent memory and collaboration now live in agentmemory; stable facts, rules, source notes, and reusable answers are promoted back into wiki/ when they deserve a durable public home.

Start Here

You are First step Then
Weiping Open Codex, Claude Code, or OpenCode Talk naturally. Agents choose skills, use agentmemory, update the wiki, and make scoped commits when useful.
A future agent Read AGENTS.md For whole-computer maintenance or local project routing, read wiki/concepts/whole-computer-project-map.md; for D-drive infrastructure detail and the WEIPING agentic constellation, read wiki/concepts/d-drive-project-map.md and wiki/concepts/weiping-agentic-project-constellation.md; for physical C:/D:/G: organization, use D:\agent-resources\skills\vipin\workstation-maintenance; then check wiki/index.md, wiki/catalog.json, and recent wiki/log.md; use agentmemory for active recall/collaboration.
A human reader Open wiki/index.md Follow entities, concepts, sources, analyses, and saved query pages.
A maintainer Run python scripts/wiki.py maintain --scope whole-computer --json Review the ignored maintenance report, make curated updates only when evidence changed, then validate before committing.

What This Repo Holds

Layer Path Purpose
Operating contract AGENTS.md, CLAUDE.md, .opencode/OPENCODE.md Rules for agent behavior, wiki edits, collaboration, skills, commits, and public/private boundaries.
Public wiki wiki/ Maintained knowledge graph: entities, concepts, topics, sources, analyses, queries, timelines, and logs.
Private layer wiki-private/ Local-only sensitive material; never indexed into the public wiki or public Git.
Raw sources raw/ Immutable public-safe source packages and manifests.
Automation scripts/ The canonical CLI is python scripts/wiki.py <command>.
Publishing site/ Quartz adapter for GitHub Pages; wiki/ remains the source of truth.
Skills .codex/skills/, .claude/skills/ Project-local skills; broader reusable skills live in D:\agent-resources.

Agentmemory-First Collaboration

The old custom Agent Hub is retired. Historical pages may still describe it, but active coordination should use agentmemory.

Agents should use:

  • memory_recall / smart search for active memory retrieval.
  • memory_save for important decisions, lessons, configurations, and findings.
  • memory_signal_send / signal reads for cross-agent handoffs.
  • action/checkpoint tools when a task needs coordination state.

Markdown files under memory/ are now a historical/superseded layer unless the user explicitly asks to work with them. Reusable public-safe knowledge should be crystallized into wiki/ pages instead of requiring every agent to dual-write session files.

Implicit Skill Routing

Agents should not wait for the user to name a skill. For non-trivial work, classify the task intent, inspect available skill metadata, read the matched SKILL.md, and follow that workflow before acting.

Primary skill roots:

Root Use
D:\agent-resources\SKILL-INDEX.md Broad curated skill index and routing map.
D:\agent-resources\skills\ Shared reusable skill library.
D:\AGENT_RESOURCE / D:\agent-resources Shared reusable skill/resource library. The lowercase path is a compatibility junction.
D:\agent-resources\skills\vipin\workstation-maintenance Shared C:/D:/G: inventory, batch-move, rollback, and agent-infrastructure sync workflow.
.codex/skills/ Codex project-local skills, including ARIS research audit workflows.
.claude/skills/ Claude Code / OpenCode-visible project skills.

Research-audit work remains strict: use the appropriate ARIS skill and preserve evidence labels, baseline boundaries, and experiment integrity.

Common Commands

python scripts/wiki.py status
python scripts/wiki.py health
python scripts/wiki.py catalog
python scripts/wiki.py lint
python scripts/wiki.py search "agentmemory"
python scripts/wiki.py context L1 --query "whole-computer maintenance"
python scripts/wiki.py maintain --scope whole-computer --json
python scripts/wiki.py obsidian export --json
python scripts/wiki.py obsidian commands --json
python scripts/wiki.py obsidian quick "whole-computer maintenance"
python scripts/wiki.py obsidian backlinks weiping-wiki-maintenance-system
python scripts/wiki.py crystallize --title "How to ingest sources" --type query --from-file notes.md
python scripts/wiki.py lifecycle --json
python scripts/wiki.py graph stats
python scripts/wiki.py graph neighbors llm-wiki --depth 1
python scripts/wiki.py search "llm wiki" --graph --semantic
python scripts/wiki.py scrub raw/inbox/new-source.md
python scripts/wiki.py health --fix --dry-run
powershell .\scripts\computer-inventory.ps1
powershell .\scripts\wiki-maintenance-audit.ps1
powershell .\scripts\wiki-maintain.ps1 -Scope whole-computer -Json
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\New-WorkstationInventory.ps1 -OutputDir ".wiki-tmp\workstation-maintenance"
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\New-MovePlan.ps1 -ManifestPath "<manifest.json>"
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\Test-MovePlanBatches.ps1 -MovePlanPath "<move-plan.json>"
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\New-ApprovalPacket.ps1 -MovePlanPath "<move-plan.json>" -PreflightSummaryPath "<preflight-summary.json>"
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\Invoke-ApprovedMoveBatch.ps1 -MovePlanPath "<move-plan.json>" -BatchId "<batch-id>" -PreflightOnly
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\New-DriveRootOrganizationPlan.ps1 -DriveRoot "D:\" -OutputDir ".wiki-tmp\workstation-maintenance"
powershell D:\agent-resources\skills\vipin\workstation-maintenance\scripts\Invoke-DriveRootOrganizationPlan.ps1 -PlanPath "<d-drive-root-plan.json>" -PreflightOnly

The file move-plan command defaults to a 30-day age gate and 100-item batch cap for live manifests; recent files are deferred for review instead of placed in executable batches. Test-MovePlanBatches.ps1 is a non-moving readiness check for every proposed batch, not approval to move files. D-root organization plans move eligible immediate root directories under D:\_Organized\<bucket>\_RootDirs\ and leave old paths as junctions; locked roots stay classified in place until a later retry. Once broad approval is granted, future agents should execute currently passing low-risk batches without asking for trivial per-batch confirmations.

Compatibility wrappers still exist for older workflows, but scripts/wiki.py is the canonical surface.

Knowledge Workflows

Workflow When Output
Answer User asks a substantive question Grounded answer from maintained pages and active memory when relevant.
Crystallize A conversation produced reusable knowledge Query, concept, analysis, source, or topic page plus log/catalog updates.
Ingest A source should become durable knowledge Source page plus linked entities, concepts, or topics.
Maintain Pages drift, duplicate, or go stale Non-destructive cleanup, supersession notes, and validation.
Publish Public wiki changes Catalog/lint checks, scoped commit, and GitHub push.

Quality Rules

  • Use the .wiki-schema.md confidence taxonomy: EXTRACTED, INFERRED, AMBIGUOUS, UNVERIFIED.
  • Preserve public/private boundaries. Public pages must not expose secrets, tokens, private chats, private docs, or sensitive personal data.
  • Keep research project claims inside their evidence gates. Do not change experiment progress, datasets, checkpoints, or server state from this repo.
  • Stage only scoped files. Existing unrelated dirty work belongs to its owner.
  • Infrastructure changes must update the relevant operating docs in the same commit.
  • Whole-computer maintenance, local project routing, or file-organization work should start from whole-computer project map; D-drive infrastructure detail stays in D-drive project map so agent runtime cleanup stays separate from research experiments. Physical drive organization must use the shared workstation-maintenance skill, produce a dry-run manifest or D-root organization plan first, defer recent files and cap file batches by default, optionally preflight the full plan, exact batch, or D-root plan, and move only approved batches with rollback manifests. Broad approval counts for all currently passing low-risk batches.
  • Continuous WEIPING_WIKI maintenance is documented in WEIPING_WIKI maintenance system. Weekly automation should use gpt-5.5 with xhigh reasoning when supported, report first, update only curated scoped files, validate, then commit and push when real evidence changed. The historical vipinknowledge-maintenance-system slug remains an alias for older links.
  • The WEIPING agentic roots are connected through WEIPING agentic project constellation: keep routes and artifact handoffs tight, but do not make repos depend on each other's private .env, cache, DB, runtime state, or generated reports.
  • Obsidian-compatible local-first features are documented in Obsidian feature parity. Use python scripts/wiki.py obsidian export --json to refresh vault config, Bases, Canvas, command palette, templates, slides home, workspaces, and the dashboard.

Related Repositories

Repo Purpose
AGENT_RESOURCE / agent-resources Public curated skills, workflows, references, and implicit skill-routing guidance.
devtools-public Clean public export of D-drive-first local agent infrastructure.
AGENTIC_SCIENCE Public agentic-science methods repository; UUPF is used as an offline audit/planning forge for major skill upgrades.
agentmemory Upstream persistent memory and MCP coordination system.

For Agents

Read AGENTS.md first. It defines the mission, source hierarchy, collaboration tone, agentmemory policy, implicit skill routing, cross-project boundaries, validation gates, and commit discipline.

Agent Hub references in older pages are historical unless explicitly marked active by a newer rule. The current operating model is agentmemory-first.

About

knowledge base managed with an LLM workflow

Resources

License

Stars

1 star

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors