Table of Contents
dsh-vk-group
DeepSeek Harness plugin for full VKontakte community management.
This wiki is the complete design and operating documentation. It is written to be read before writing any code — every page states what must exist, what the platform allows, and where the traps are.
Start here
| Page | Read it when |
|---|---|
| Architecture | you need the module layout and the DSH extension points used |
| Platform-DSH | you are writing plugin code and need the Cordis/DSH contract |
| Platform-VK-API | you are writing a VK call and need the actual constraints |
| Tools-Reference | you need the exact argument and output shape of a tool |
| Configuration | you are deploying the plugin |
| LongPoll-and-Events | you are working on the event bridge |
| Moderation-Engine | you are working on the rule engine |
| Security-Model | you are reviewing what the agent is allowed to do |
| Testing-Strategy | you are writing tests |
| Roadmap | you want the implementation order and issue map |
| Non-Goals | someone asks for a feature that is out of scope |
| Glossary | a term is unclear |
| FAQ | a decision looks arbitrary |
One-paragraph summary
The plugin is a DSH bundle: an npm package with dsh.bundle.patch pointing at a cordis.patch.yml layer that inserts one plugin row. That row's apply(ctx, config) registers 30 tools on ctx.tools, starts a LongPoll background job on ctx.jobs, installs a tools/pre-execute policy gate plus a monotonic ctx.tools.guard(), writes an audit log to ctx.storage, contributes a system-prompt section, and ships a skill. VK access goes through one client module that owns the token bucket, the retry/backoff policy, and the error-code mapping, so no tool ever talks to HTTP directly.
Status
| Design | complete |
| Wiki | complete |
| Issues | filed, one per work package |
| Code | not started |