L4StrategyDirection · Budget · Red LinesSTP + Market Research
Machine (Left Track)
Meta Analysis (CDA/Framenet)
Public sentiment scan
Compute value assessment
Human (Right Track)
Define Brand Soul
Set compliance red lines
Approve monthly compute budget
🛡 Risk Auto-block political/extreme topics📦 Asset Raw sentiment data → labeled storage💰 Cost Allocate budget per track, cut ROI<1 topicsOutput: Strategy CharterCompute Budget
↓
L3ProductCategory · Asset · ROI4P - Product
Machine (Left Track)
Competitor deconstruction (TOP10)
Association rule mining for high-conversion angles
Generate product prototypes
Human (Right Track)
Decide SKU format
Approve core selling points
Review corpus ingestion standards
🛡 Risk Product compliance screening📦 Asset Clean data → private corpus / brand lexicon💰 Cost Cap investment, target >=60% gross marginOutput: PRDPrivate Corpus Index
🛡 Risk Filter sensitive cases/violations📦 Asset New material → vector DB💰 Cost Prioritize local vector DB, reduce external APIOutput: Context Package
↓
L1GenerationProduce · Control Token · Quality4P - Promotion
Machine (Left Track)
Load Skill template + assemble Prompt
LLM batch generation + cache
Auto-filter violating drafts
Human (Right Track)
Tweak Skill params (sarcasm/meme density)
Spot-check output quality
Reject substandard content
🛡 Risk Machine pre-check sensitive words + human final review📦 Asset High-quality drafts / golden sentences → storage💰 Cost Select model by value, cache reuse >=40%Output: Content Draft
🛡 Risk Real-time platform rule monitoring → fuse📦 Asset User feedback / high-rated comments → storage💰 Cost Calculate net profit, adjust budgetOutput: Delivered AssetROI Review ReportStrategy Adjustment Order
↑ Feedback → Review → Anchor Tune
Tech Core Mapping
Computational LinguisticsCDA / FramenetL4 / L1Value identification · Tone consistency
Machine LearningClustering / Association Rules / RLL3 / L0Hit mining · ROI optimization
Computer ScienceVector DB / RAG / LLM / SkillL2 / L1Precise retrieval · Industrial production · Cost control
Risk Rules / Private Corpus / Compute AuditHard to copy
Human-in-the-Loop Boundary (L4→L0)Hard to learn
Tactics tune quality · Strategy locks trackHard to penetrate
Main Pipeline (Production)Feedback Flow (Dual Loop)Governance Flow (Cross-cutting)
External Input
Task (raw question/topic)
Router
Routing Ticket
Asset / RAG
Context Package
Executor
Draft + cost + risk_flags
Governance
Approved Draft
Approval Gate
Approved Content
Delivery
GovernanceRed-line table management · Sensitive-word filtering · Token/API quota tracking · Audit loggingAOP / Middleware cross-cuts all components, does not block flow nodes · Software shell for the 3 beams (Risk + Asset + Cost)
Event BusDecouples inter-layer communication, carries the dual-loop event-driven mechanism · Bull/BullMQ or Redis Streams or RabbitMQ
task.donetask.posteduser.reactedanchor.patch
→ Asset / RAGUser feedback/high-rated comments → ingest→ RouterAnchor patch (human review → merge)→ KnobsROI signal → human tuning
Approval GateCertain types require human approval before publishing (L0 final review / L3 product decision)Async approval queue — human approves/rejects via Dashboard or notificationHuman right-track Approval Gate
KnobsHuman can adjust Skill params, anchor weights, red-line table (without changing code)Web Dashboard or CLI commandHuman right-track Tuning Knob
Private corpusCompute calibration modelRisk control baselineVertical LLM
3. How Do Human and AI Collaborate?
Human anchors, machines executeControlled pipelineHard gatesParameter tuning intervention
4. What Drives It Beyond Philosophy?
A bidirectional closed-loop systemA data-driven engineAn agentic hubAn omni-integration base
02Field-tested: one night, machines finished the job
Human sets the anchor, machines run the line — zero manual operation
The framework applied as a fully automated workflow: machines found their own way, filled in the details, submitted, and reported back; the human only set goals and answered when asked. Every number comes from a real run ledger, replayable line by line.
Results
A full night unattended, running on its ownOver half of attempts reached the finish line; the rest were targets already goneTechnical failures: 010,000+ task sources, 638 stale entries auto-purged
Who does what
Machines: navigate · fill · submit · reportHuman: set goals · watch progress · step in when askedCAPTCHA: machines stop and ask, never guessDisconnect: resume from the breakpoint, start over never
How it was done
No hardcoded scripts; agents adapt on the spotEvery step logged, replayable, auditableFailures are ledgered too, so the same one never repeatsCut losses: one route failed 16 times — switched routes
From minimal framework to full capability structure