Notebook Initial Setup and chulbuji.com Operating Standards Test
Background
I created the first Notebook to accumulate chulbuji.com operating standards and project context.
The purpose of this work was to check whether Notebook could be used not just as a writing tool, but as a source-based workspace that remembers and reviews the operating standards for chulbuji.com.
Sources Added
The initial Notebook included the following standard documents as sources.
- chulbuji.com Operating Standards v0.1
- chulbuji.com Major Project Separation Criteria v0.1
- chulbuji.com Log / Insight Writing Standards v0.1
- AI Role Assignment and Vibe Coding Standards v0.1
- Codex Limited Content Reflection Standards v0.1
- Notebook Usage Standards v0.1
What Was Tested
Using the added sources, I checked whether Notebook understood the core operating structure of chulbuji.com.
The main test items were:
- Distinguishing the roles of Log, Insight, Project, and Board
- Separating AI Content Assistant from InsightReport
- Assigning roles among Meta Chulbuji, Claude Code, Codex, and Notebook
- Creating vibe coding instructions for Claude Code
- Creating read-only review checklists for Codex
- Checking the criteria for separating today’s learning into Log and Insight
Result
Notebook was able to distinguish Log and Insight relatively reliably based on the chulbuji.com operating standards.
It also separated AI Content Assistant and InsightReport by purpose, current status, button labels, and prohibited wording.
It also confirmed that Claude Code can be assigned to structural changes and implementation, Codex to read-only review and limited content reflection, and Notebook to standards memory and consistency review.
Next Action
The judgment and operating principles learned today will be separated into a dedicated Insight article.
Next, I will expand Notebook’s role by using it to create chulbuji.com article drafts, instructions, and review checklists, then checking their consistency against the existing operating standards.