A record of building a local MVP with Claude Code that converts photos and short clips into 9:16 vertical MP4s. Covers the step-by-step feature expansion from v0.1.0 to v0.1.4, the Phase 1 completion criteria, and what was deferred to Phase 2.
After fixing partial take-profit, the real question was whether the state actually carried through. PARTIAL_SELL firing is one thing. But does partial_sold=True get saved? Does the next loop read it and prevent a second trigger? Does the remaining position stay under trailing stop management? This log tracks those verifications step by step.
Partial take-profit was enabled, the rule_engine logic was implemented, and the thresholds were configured. But the intraday 5-minute sell loop was calling check_sell_signal without passing the actual position size or partial_sold state — so PARTIAL_SELL could structurally never be returned. The fix wasn't in the strategy logic. It was rewiring the scheduler's call.
Until May, I mostly used conversations with Meta Chulbuji to clarify direction and execute projects. In June, I am shifting toward a repeatable AI operating system using harnesses, skills, workflows, and evals across AI Content Assistant, AdSense preparation, chulbuji.com, and auto-trading records.
Recent losses made me review whether the trading conditions should change. Instead of changing them immediately, I first found look-ahead bias and universe bias in the backtest, kept the current rules, and added logs plus a shadow_report structure for observation.
Followed Builder Josh's YouTube course to run hands-on Codex practice covering plugins, skills, DESIGN.md-based UI work, and the $pdca flow. Key takeaway: AI agents move autonomously through the entire task, so the human needs to design clear stop conditions at each stage.
Took the Codex Master Class learnings into an actual project. Ran the full Deep Interview → Plan → Design → Do → GitHub → Cloudflare sequence and registered Commit Hero as Codex experiment 001 in the chulbuji.com Vibe Coding Lab.
Four scans ran in live mode but zero orders were placed. Six BUY signals fired, yet no stock passed the RS filter. Suspected ETF benchmark skew, compared four universe metrics, found the skew exists inside our own universe too. Built a D+1/D+3/D+5 tracker for rejected stocks instead of changing the logic.
A record of building the first Agent Boss Board v0.1 prototype and setting up PC2 as a secondary development and operation environment for chulbuji.com.
Verified that the AI Content Assistant service is live and purchasable from a buyer's perspective on Kmong. Service approval confirmed, 5 auto-reply FAQs configured, paid ads deferred — entering the sales validation stage.
Four fixes in response to GSC 'Crawled - currently not indexed': hreflang restoration, noindex sitemap exclusion, trailing slash normalization, and KO/EN content alignment.
Drafted a shorts script with NotebookLM, generated AI video clips with Google Vids/Veo, and added subtitles and narration to validate the first end-to-end shorts production workflow. The goal was not monetization — it was finding out whether a repeatable shorts production SOP is achievable.
Root-cause analysis of repeated zero-buy days during KOSPI surges, and a strategy engine overhaul that switches MA20 deviation thresholds dynamically based on BULL / NEUTRAL / BEAR market regime detection.
A strategy engine refinement log for the stock auto-trading program, based on live-account operating data: capital structure, stop-loss rules, target profit, sector overlap limits, and profit-risk analysis log placement.
A record of registering as a seller on Kmong (Korea's freelance marketplace) and listing the first product to validate whether the AI Content Assistant service can sell. Currently pending approval.
A record of creating the first Notebook for chulbuji.com operations, adding operating standards, project separation rules, and AI role assignment criteria as sources, then checking its baseline understanding.
After comparing three brand symbol concepts for chulbuji.com, Concept 3 was chosen as the main logo, Concept 1 as the favicon and secondary symbol, and Concept 2 was excluded from this brand system.
An operations log covering the first trading day after the weekend upgrade to the Korean stock auto-trading program, including the move toward a ₩10M seed structure.
The AI Blog / AdSense experiment had been managed alongside the monthly operating Board — but running it over time made clear it needed its own project page as a long-term record hub on chulbuji.com.
The tool felt unfamiliar at first and took real effort to work through — but the video got finished and uploaded. A small but meaningful comparison experiment is now in place: a dynamic video alongside a static image video of the same track.
Defined the v2.0 upgrade direction for a more production-ready system. Seven improvement areas: zero-order bug after BUY signal, available-cash API errors, high-priced stock handling, ratio-based capital allocation, market-strength-based entry count, DRY RUN vs LIVE mode clarity, and API retry/fallback. Built through vibe coding: expert AI for analysis, Claude Code for implementation.
Two live trading days. Weekly realized P&L: +₩40,658. Trailing stop hit three consecutive wins (zero stop-losses). Closing portfolio value ₩4,928,266 — down ₩13,941 from the week's start on unrealized P&L.
Live account day 9. LG Chem's trailing stop triggered for the first time in range A (+3–6%) — auto-sold at ₩393,500, +2.88% gain. Total valuation ₩4,948,738, daily realized P&L +₩11,000. All holdings closed in the green.
KOSPI hit an intraday record. 4 of my 5 positions were in the red. The system was filling MAX_HOLD=5 slots in order of qualification, not strength. Added an RS filter and removed forced slot-filling. Running BUY_DRY_RUN=True for 2–3 trading days.
Confirmed Firebase Studio end-of-service. Migrated the chulbuji.com development environment to local VS Code on an LG Gram. Cloned the repo, confirmed the build, cleaned up the Astro 5 content config, and pushed to main. Local → GitHub → Cloudflare auto-deploy pipeline secured.
VS Code + Claude Code install, Next.js + TypeScript + Tailwind CSS project, GitHub + Cloudflare Pages pipeline, 8 screens implemented, OpenAI GPT-4o API connected, live service deployed — all in one day. 23 seconds from git push to production.
Three bugs in the KIS live auto-trading system — wrong cash field reference, 18 duplicate sell orders for KT, misplaced code fix. All found and fixed the same day. You don't need to read code to debug. Read logs, describe what's off, let AI trace the cause.
An idea sketched into a business plan application became a mobile interactive prototype in a single day using Claude Design. v1 feedback led to v2, and it was only after seeing the screens that the MVP scope and dev environment direction became clear.
Live day 3. KB Financial and Kakao hit the -3% stop-loss, -₩61,800 total. MA60 filter correctly blocked 3 downtrend stocks (NAVER, Kia, Hyundai Motor) — first real-money validation after the 4/21 API replacement. Budget safety margin: success at 13:00, failed again at 14:00. KT entered as new position. Closing balance ₩4,906,290.
AutoTradingLiveAccountStopLossMA60BudgetSafetyMarginKIS API
First day on the live account. Two morning bugs resolved (cached paper token / MA60 data shortage), first buys executed at 10:33. Five stocks — Kakao, Kia, KB Financial, Shinhan, NAVER — ₩4,690,300 deployed. End-of-day unrealized P&L: –₩54,030 (–1.08%), all 5 positions held.
Four days of first live operations. DRY RUN validation → first buy → first trailing stop trigger → lock file failure recovery → universe expanded to 20 stocks. Weekly realized P&L: +₩15,000. Total portfolio: ₩10,037,479.
10:30 AM. Kakao, 20 shares @ ₩48,350. The system that ran in DRY_RUN mode is now live. Three fixes before the open, trailing activation logs and Telegram position summary in the afternoon, --live flag added to the scheduler.
Two months after the rebrand, records started piling up and the structure needed to follow. A log of the transition from intro site to long-term asset architecture.
Yesterday evening, two hours. Fixed a cash balance field bug, added retry logic, duplicate prevention, improved RSI, and introduced a trailing stop. A confirmation that systems can change this much without writing the code yourself.
The code was updated, but the process was still running on yesterday's state. Found the root cause, patched the MA60 gap in the paper trading environment with a fallback, and restored the DRY_RUN buy cycle.
After implementing the coaching-focused MVP, I ran a 500m indoor test. Identified three issues: unresponsive start button, mismatched voice coaching due to missing GPS data, and a coaching interval mismatch with the test distance. Each root cause was isolated and fixed. The patched build gets validated in an outdoor run tomorrow.
Visitors were reading for an average of 2 minutes, but not a single click on the CTA. Here's why I changed 'Start for Free' to 'Organize My Thoughts for Free' — and the hypothesis behind it.
A solo maker who can't write a single line of code successfully tracked button clicks with GA4+GTM two days before the hackathon. Chulbuji designed what to measure, Meta-chulbuji implemented it. Now I don't guess — I prove.
From seeing an ad and thinking 'I want to try this' to asking Meta-chulbuji, executing through mistakes, and completing my first song 'Chuno: The Outcry' with a channel launch in just 2 hours
Dual BrainWhisperingRocket JumpMurekaKorean Traditional FusionMeta-chulbujiAI FreshmanPlusHumanMistakes as Process
I share my experience of escaping 'Tutorial Hell' and launching my first AI product, the 'Meta-chulbuji Report,' by collaborating with AI as a 'Plus-Human'.
A semiconductor engineer with 34 years of experience documents the complete process of rebranding chulbuji.com to grow as a Product Builder alongside AI.
This site uses cookies for service improvement and advertising (Google AdSense). By continuing to use this site, you agree to our use of cookies. Privacy Policy