Problem
- delivery-partner and 3PL pricing policies and BPM rules were split across several wikis
- There was no structure that new members and AI tools could both reuse
Company
OnePiece Knowledge Base & Answer Viewer
Policies and operating logic scattered across wikis, structured into a knowledge base for both people and MCP
Period | 2026.07 ~ 2026.08
Pricing policies and operating logic scattered across wikis
-
Policies and logic
BeforePricing policies and operating logic scattered across wikis
AfterOne trigger-action knowledge base (11 rules)
My Role
- Consolidated pricing policies and 11 BPM rules into a trigger-action structure
- Structured terms, formulas, issues and related projects so MCP can reuse them
- Built an Answer Viewer that saves answers as local Markdown, renders HTML and files feedback as GitHub issues
Result
- Runs on premises, lowering privacy and security risk while closing the feedback loop
- A shared knowledge source for onboarding and MCP-based Q&A
Technical Decisions
On-premises environment
Answers are stored and viewed inside the company environment to lower privacy and security risk
Structured for MCP reuse
New members and AI tools share the same terms, formulas and issues
