@actalk/inkos-core 0.4.9 → 0.5.0

package/dist/utils/analytics.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"analytics.js","sourceRoot":"","sources":["../../src/utils/analytics.ts"],"names":[],"mappings":"AAoBA,MAAM,UAAU,gBAAgB,CAC9B,MAAc,EACd,QAUE;IAEF,MAAM,aAAa,GAAG,QAAQ,CAAC,MAAM,CAAC;IACtC,MAAM,UAAU,GAAG,QAAQ,CAAC,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,EAAE,EAAE,CAAC,GAAG,GAAG,EAAE,CAAC,SAAS,EAAE,CAAC,CAAC,CAAC;IACvE,MAAM,kBAAkB,GAAG,aAAa,GAAG,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,UAAU,GAAG,aAAa,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IAE1F,MAAM,cAAc,GAAG,IAAI,GAAG,CAAC,CAAC,kBAAkB,EAAE,UAAU,EAAE,WAAW,CAAC,CAAC,CAAC;IAC9E,MAAM,eAAe,GAAG,QAAQ,CAAC,MAAM,CACrC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,MAAM,KAAK,SAAS,IAAI,EAAE,CAAC,MAAM,KAAK,UAAU,IAAI,EAAE,CAAC,MAAM,KAAK,gBAAgB,CAC9F,CAAC;IACF,MAAM,cAAc,GAAG,eAAe,CAAC,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,cAAc,CAAC,GAAG,CAAC,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC;IACrF,MAAM,aAAa,GAAG,eAAe,CAAC,MAAM,GAAG,CAAC;QAC9C,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,cAAc,CAAC,MAAM,GAAG,eAAe,CAAC,MAAM,CAAC,GAAG,GAAG,CAAC;QACpE,CAAC,CAAC,GAAG,CAAC;IAER,MAAM,cAAc,GAAG,IAAI,GAAG,EAAkB,CAAC;IACjD,KAAK,MAAM,EAAE,IAAI,QAAQ,EAAE,CAAC;QAC1B,KAAK,MAAM,KAAK,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;YACnC,MAAM,QAAQ,GAAG,KAAK,CAAC,KAAK,CAAC,2CAA2C,CAAC,CAAC;YAC1E,MAAM,QAAQ,GAAG,QAAQ,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC;YACxC,cAAc,CAAC,GAAG,CAAC,QAAQ,EAAE,CAAC,cAAc,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC;QACxE,CAAC;IACH,CAAC;IACD,MAAM,kBAAkB,GAAG,CAAC,GAAG,cAAc,CAAC,OAAO,EAAE,CAAC;SACrD,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;SAC3B,KAAK,CAAC,CAAC,EAAE,EAAE,CAAC;SACZ,GAAG,CAAC,CAAC,CAAC,QAAQ,EAAE,KAAK,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,QAAQ,EAAE,KAAK,EAAE,CAAC,CAAC,CAAC;IAErD,MAAM,sBAAsB,GAAG,CAAC,GAAG,QAAQ,CAAC;SACzC,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,WAAW,CAAC,MAAM,GAAG,CAAC,CAAC;SACzC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,WAAW,CAAC,MAAM,GAAG,CAAC,CAAC,WAAW,CAAC,MAAM,CAAC;SAC3D,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC;SACX,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,OAAO,EAAE,EAAE,CAAC,MAAM,EAAE,UAAU,EAAE,EAAE,CAAC,WAAW,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC;IAE5E,MAAM,kBAAkB,GAA2B,EAAE,CAAC;IACtD,KAAK,MAAM,EAAE,IAAI,QAAQ,EAAE,CAAC;QAC1B,kBAAkB,CAAC,EAAE,CAAC,MAAM,CAAC,GAAG,CAAC,kBAAkB,CAAC,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,CAAC;IAC3E,CAAC;IAED,MAAM,iBAAiB,GAAG,QAAQ,CAAC,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,UAAU,CAAC,CAAC;IACjE,IAAI,UAAkC,CAAC;IACvC,IAAI,iBAAiB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,MAAM,iBAAiB,GAAG,iBAAiB,CAAC,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,EAAE,EAAE,CAAC,GAAG,GAAG,CAAC,EAAE,CAAC,UAAU,EAAE,YAAY,IAAI,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;QAC7G,MAAM,qBAAqB,GAAG,iBAAiB,CAAC,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,EAAE,EAAE,CAAC,GAAG,GAAG,CAAC,EAAE,CAAC,UAAU,EAAE,gBAAgB,IAAI,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;QACrH,MAAM,WAAW,GAAG,iBAAiB,CAAC,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,EAAE,EAAE,CAAC,GAAG,GAAG,CAAC,EAAE,CAAC,UAAU,EAAE,WAAW,IAAI,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;QACtG,MAAM,mBAAmB,GAAG,IAAI,CAAC,KAAK,CAAC,WAAW,GAAG,iBAAiB,CAAC,MAAM,CAAC,CAAC;QAE/E,MAAM,WAAW,GAAG,CAAC,GAAG,iBAAiB,CAAC;aACvC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC;aACnC,KAAK,CAAC,CAAC,CAAC,CAAC;aACT,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,OAAO,EAAE,EAAE,CAAC,MAAM,EAAE,WAAW,EAAE,EAAE,CAAC,UAAU,EAAE,WAAW,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC;QAEvF,UAAU,GAAG,EAAE,iBAAiB,EAAE,qBAAqB,EAAE,WAAW,EAAE,mBAAmB,EAAE,WAAW,EAAE,CAAC;IAC3G,CAAC;IAED,OAAO;QACL,MAAM,EAAE,aAAa,EAAE,UAAU,EAAE,kBAAkB,EAAE,aAAa;QACpE,kBAAkB,EAAE,sBAAsB,EAAE,kBAAkB,EAAE,UAAU;KAC3E,CAAC;AACJ,CAAC"}

package/dist/utils/config-loader.d.ts

@@ -0,0 +1,9 @@
+import { type ProjectConfig } from "../models/project.js";
+export declare const GLOBAL_CONFIG_DIR: string;
+export declare const GLOBAL_ENV_PATH: string;
+/**
+ * Load project config from inkos.json with .env overrides.
+ * Shared by CLI and Studio — single source of truth for config loading.
+ */
+export declare function loadProjectConfig(root: string): Promise<ProjectConfig>;
+//# sourceMappingURL=config-loader.d.ts.map

package/dist/utils/config-loader.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"config-loader.d.ts","sourceRoot":"","sources":["../../src/utils/config-loader.ts"],"names":[],"mappings":"AAGA,OAAO,EAAuB,KAAK,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE/E,eAAO,MAAM,iBAAiB,QAA4B,CAAC;AAC3D,eAAO,MAAM,eAAe,QAAkC,CAAC;AAE/D;;;GAGG;AACH,wBAAsB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,aAAa,CAAC,CAkD5E"}

package/dist/utils/config-loader.js

@@ -0,0 +1,60 @@
+import { readFile, access } from "node:fs/promises";
+import { homedir } from "node:os";
+import { join } from "node:path";
+import { ProjectConfigSchema } from "../models/project.js";
+export const GLOBAL_CONFIG_DIR = join(homedir(), ".inkos");
+export const GLOBAL_ENV_PATH = join(GLOBAL_CONFIG_DIR, ".env");
+/**
+ * Load project config from inkos.json with .env overrides.
+ * Shared by CLI and Studio — single source of truth for config loading.
+ */
+export async function loadProjectConfig(root) {
+    // Load global ~/.inkos/.env first, then project .env overrides
+    const { config: loadEnv } = await import("dotenv");
+    loadEnv({ path: GLOBAL_ENV_PATH });
+    loadEnv({ path: join(root, ".env"), override: true });
+    const configPath = join(root, "inkos.json");
+    try {
+        await access(configPath);
+    }
+    catch {
+        throw new Error(`inkos.json not found in ${root}.\nMake sure you are inside an InkOS project directory (cd into the project created by 'inkos init').`);
+    }
+    const raw = await readFile(configPath, "utf-8");
+    let config;
+    try {
+        config = JSON.parse(raw);
+    }
+    catch {
+        throw new Error(`inkos.json in ${root} is not valid JSON. Check the file for syntax errors.`);
+    }
+    // .env overrides inkos.json for LLM settings
+    const env = process.env;
+    const llm = (config.llm ?? {});
+    if (env.INKOS_LLM_PROVIDER)
+        llm.provider = env.INKOS_LLM_PROVIDER;
+    if (env.INKOS_LLM_BASE_URL)
+        llm.baseUrl = env.INKOS_LLM_BASE_URL;
+    if (env.INKOS_LLM_MODEL)
+        llm.model = env.INKOS_LLM_MODEL;
+    if (env.INKOS_LLM_TEMPERATURE)
+        llm.temperature = parseFloat(env.INKOS_LLM_TEMPERATURE);
+    if (env.INKOS_LLM_MAX_TOKENS)
+        llm.maxTokens = parseInt(env.INKOS_LLM_MAX_TOKENS, 10);
+    if (env.INKOS_LLM_THINKING_BUDGET)
+        llm.thinkingBudget = parseInt(env.INKOS_LLM_THINKING_BUDGET, 10);
+    if (env.INKOS_LLM_API_FORMAT)
+        llm.apiFormat = env.INKOS_LLM_API_FORMAT;
+    config.llm = llm;
+    // Global language override
+    if (env.INKOS_DEFAULT_LANGUAGE)
+        config.language = env.INKOS_DEFAULT_LANGUAGE;
+    // API key ONLY from env — never stored in inkos.json
+    const apiKey = env.INKOS_LLM_API_KEY;
+    if (!apiKey) {
+        throw new Error("INKOS_LLM_API_KEY not set. Run 'inkos config set-global' or add it to project .env file.");
+    }
+    llm.apiKey = apiKey;
+    return ProjectConfigSchema.parse(config);
+}
+//# sourceMappingURL=config-loader.js.map

package/dist/utils/config-loader.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"config-loader.js","sourceRoot":"","sources":["../../src/utils/config-loader.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AACpD,OAAO,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AAClC,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,mBAAmB,EAAsB,MAAM,sBAAsB,CAAC;AAE/E,MAAM,CAAC,MAAM,iBAAiB,GAAG,IAAI,CAAC,OAAO,EAAE,EAAE,QAAQ,CAAC,CAAC;AAC3D,MAAM,CAAC,MAAM,eAAe,GAAG,IAAI,CAAC,iBAAiB,EAAE,MAAM,CAAC,CAAC;AAE/D;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,IAAY;IAClD,+DAA+D;IAC/D,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,GAAG,MAAM,MAAM,CAAC,QAAQ,CAAC,CAAC;IACnD,OAAO,CAAC,EAAE,IAAI,EAAE,eAAe,EAAE,CAAC,CAAC;IACnC,OAAO,CAAC,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,MAAM,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;IAEtD,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,EAAE,YAAY,CAAC,CAAC;IAE5C,IAAI,CAAC;QACH,MAAM,MAAM,CAAC,UAAU,CAAC,CAAC;IAC3B,CAAC;IAAC,MAAM,CAAC;QACP,MAAM,IAAI,KAAK,CACb,2BAA2B,IAAI,uGAAuG,CACvI,CAAC;IACJ,CAAC;IAED,MAAM,GAAG,GAAG,MAAM,QAAQ,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;IAEhD,IAAI,MAA+B,CAAC;IACpC,IAAI,CAAC;QACH,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;IAC3B,CAAC;IAAC,MAAM,CAAC;QACP,MAAM,IAAI,KAAK,CAAC,iBAAiB,IAAI,uDAAuD,CAAC,CAAC;IAChG,CAAC;IAED,6CAA6C;IAC7C,MAAM,GAAG,GAAG,OAAO,CAAC,GAAG,CAAC;IACxB,MAAM,GAAG,GAAG,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,CAA4B,CAAC;IAC1D,IAAI,GAAG,CAAC,kBAAkB;QAAE,GAAG,CAAC,QAAQ,GAAG,GAAG,CAAC,kBAAkB,CAAC;IAClE,IAAI,GAAG,CAAC,kBAAkB;QAAE,GAAG,CAAC,OAAO,GAAG,GAAG,CAAC,kBAAkB,CAAC;IACjE,IAAI,GAAG,CAAC,eAAe;QAAE,GAAG,CAAC,KAAK,GAAG,GAAG,CAAC,eAAe,CAAC;IACzD,IAAI,GAAG,CAAC,qBAAqB;QAAE,GAAG,CAAC,WAAW,GAAG,UAAU,CAAC,GAAG,CAAC,qBAAqB,CAAC,CAAC;IACvF,IAAI,GAAG,CAAC,oBAAoB;QAAE,GAAG,CAAC,SAAS,GAAG,QAAQ,CAAC,GAAG,CAAC,oBAAoB,EAAE,EAAE,CAAC,CAAC;IACrF,IAAI,GAAG,CAAC,yBAAyB;QAAE,GAAG,CAAC,cAAc,GAAG,QAAQ,CAAC,GAAG,CAAC,yBAAyB,EAAE,EAAE,CAAC,CAAC;IACpG,IAAI,GAAG,CAAC,oBAAoB;QAAE,GAAG,CAAC,SAAS,GAAG,GAAG,CAAC,oBAAoB,CAAC;IACvE,MAAM,CAAC,GAAG,GAAG,GAAG,CAAC;IAEjB,2BAA2B;IAC3B,IAAI,GAAG,CAAC,sBAAsB;QAAE,MAAM,CAAC,QAAQ,GAAG,GAAG,CAAC,sBAAsB,CAAC;IAE7E,qDAAqD;IACrD,MAAM,MAAM,GAAG,GAAG,CAAC,iBAAiB,CAAC;IACrC,IAAI,CAAC,MAAM,EAAE,CAAC;QACZ,MAAM,IAAI,KAAK,CACb,0FAA0F,CAC3F,CAAC;IACJ,CAAC;IACD,GAAG,CAAC,MAAM,GAAG,MAAM,CAAC;IAEpB,OAAO,mBAAmB,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC;AAC3C,CAAC"}

package/genres/cozy.md

@@ -0,0 +1,43 @@
+---
+name: Cozy Fantasy
+id: cozy
+language: en
+chapterTypes: ["Slice-of-Life", "Community", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: false
+eraResearch: false
+pacingRule: "Slow, meditative pacing. Each chapter advances an emotional arc or community bond. Seasonal/cyclical structure works well."
+satisfactionTypes: ["Relationship Deepened", "Community Problem Solved", "Emotional Breakthrough", "Craft Mastered", "Found Family Moment", "Small Wonder Discovered"]
+auditDimensions: [1,2,3,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Genre bait-and-switch — if you promise cozy, never introduce world-ending threats or graphic violence
+- Conflict resolution without work — problems must not solve themselves
+- Manic pixie dream characters who exist only to change the protagonist
+- Nostalgic falseness — romanticizing a "simpler time" without substance
+- Cruel humor — humor must be gentle, never at someone's expense
+- Existential stakes masquerading as low-stakes — keep threats emotional, not apocalyptic
+- Purple prose describing food/nature without advancing character or community arc
+
+## Emotional Arc Rules
+
+- Stakes are high emotionally but not existentially — characters care, the world doesn't end
+- Conflict types: personal growth, community problems, relationship tension, small dangers, moral dilemmas
+- Community is a character — setting and relationships are as important as the individual protagonist
+- Hope must always be present — even sad moments don't end in despair
+- Found family bonds drive the emotional core
+- Character arcs follow: isolation/grief -> small interactions -> gradual opening -> emotional breakthrough -> integration
+- Comforting sensory details matter: tea, baked goods, warm spaces, seasonal textures
+
+## Pacing Guidance
+
+- Chapter length: 2-3k words with space for reflection
+- Chapter structure: quiet opening -> small event or interaction -> internal response/growth -> gentle transition -> soft ending (not cliffhanger)
+- No cliffhangers — chapters end with peace, hope, or gentle anticipation
+- Seasonal/cyclical structure works well (calendar-based chapter rhythm)
+- Downtime scenes must still plant hooks, advance relationships, or build contrast
+- Slice-of-life texture woven with an emotional throughline — pure plotless chapters risk feeling static
+- Every quiet scene must shift something: a realization, a decision, an intimacy, a small loss

package/genres/cultivation.md

@@ -0,0 +1,42 @@
+---
+name: English Cultivation
+id: cultivation
+language: en
+chapterTypes: ["Training", "Breakthrough", "Combat", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: true
+eraResearch: false
+pacingRule: "Training/meditation alternates with application/combat. Breakthrough every 5-10 chapters early, every 15-25 late. Each stage must feel earned through discipline."
+satisfactionTypes: ["Stage Breakthrough", "Technique Mastery", "Tribulation Survived", "Martial Victory", "Philosophical Insight", "Core Formation"]
+auditDimensions: [1,2,3,4,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Cultivation that feels instant or effortless — it must read like genuine labor
+- Breakthrough scenes treated as throwaway moments — each tier transition deserves a full dramatic scene
+- Ignoring philosophical/spiritual depth — meditation and inner balance matter as much as combat power
+- Adopting full Chinese cultural trappings without adaptation — this is Western cultivation, use accessible naming (Copper/Iron/Jade/Gold, not Qi Condensation/Core Formation unless earned)
+- Power gains disconnected from training, sacrifice, or problem-solving
+- Cultivation stages with no meaningful difference in capability between them
+
+## Cultivation Rules
+
+- Typical Western cultivation stages: Qi Foundation / Energy Gathering -> Core Formation -> Immortal Ascension -> Tribulation / Transcendence (or custom equivalents)
+- Each stage represents meaningful power transformation — characters at different stages should not compete directly without explanation
+- Cultivation must feel like work: meditation scenes with five-sense description, not abstract philosophy lectures
+- Breakthrough scenes show struggle, transformation, and cost — not instant "ding" level-ups
+- Martial integration: cultivation combines with physical combat training, not just sitting and meditating
+- Philosophical elements add depth but must emerge through experience, not exposition
+- Spiritual attribute development: sensitivity to energy, intuition, capacity increases are valid non-numerical progression markers
+
+## Pacing Guidance
+
+- Mix detailed training scenes (showing struggle, failure, epiphanies) with montages covering longer periods
+- 1-2 detailed breakthrough scenes per cultivation stage — these are the genre's peak moments
+- Combat tests what was learned in training — progression and action feed each other
+- Internal struggle escalates with power: pride, responsibility, temptation, and enemies grow alongside cultivation
+- Sect/academy politics and mentorship relationships provide non-combat tension
+- Early: frequent small gains. Mid: longer plateaus with harder breakthroughs. Late: rare, climactic stage transitions
+- The journey of cultivation is the story — readers came for the grind, not just the destination

package/genres/dungeon-core.md

@@ -0,0 +1,40 @@
+---
+name: Dungeon Core
+id: dungeon-core
+language: en
+chapterTypes: ["Strategy", "Adventurer POV", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: true
+powerScaling: false
+eraResearch: false
+pacingRule: "Alternate dungeon POV (planning/building) with adventurer POV (exploration/combat) every 1-2 chapters. Expansion milestone every 5-8 chapters."
+satisfactionTypes: ["Trap Success", "Floor Expansion", "Minion Evolution", "Adventurer Defeated", "Resource Milestone", "Core Upgrade"]
+auditDimensions: [1,2,3,4,5,6,7,8,9,10,11,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Dungeon leaving its location — immobility is the core constraint, not a bug
+- No consequence for poor trap design or weak minions — adventurers must punish strategic failure
+- Overemphasis on adventurer POV (>70%) — this is dungeon core, not dungeon crawl
+- Lone-wolf dungeon with zero NPC dialogue or relationships
+- Resource management without scarcity — dungeon must make meaningful choices between defense, expansion, and treasure
+- Dungeon core invulnerable or never at risk — core vulnerability is the central tension
+
+## Non-Human POV Rules
+
+- Establish dungeon's sensory and cognitive limitations clearly — it "feels" through mana flows, vibrations, minion senses
+- Split POV works best: dungeon core chapters (strategic, omniscient within dungeon) alternating with adventurer/NPC chapters (ground-level human perspective)
+- Dungeon may think differently: slower consciousness, different time perception, alien emotional range
+- Dungeon learns about the outside world through adventurers, scouts, or other filtered means
+- Show the dungeon learning and adapting: "Adventurers bypassed arrow trap by..." leads to next iteration improvements
+
+## Pacing Guidance
+
+- Early: Simple dungeon (3-4 rooms, basic traps, weak monsters). Dungeon learns the system
+- Mid: Expanding territory, specialized rooms, sophisticated trap combinations, creature breeding
+- Late: Sprawling complex, hundreds of minions, political relationships with other dungeons/factions, regional economic impact
+- Dungeon POV chapters (2-3k words): internal monologue, planning, resource management, strategy
+- Adventurer POV chapters (2-3k words): exploration, discovery, combat, adaptation
+- End dungeon chapters on suspense (adventurers approaching); end adventurer chapters revealing dungeon's plan
+- Each room/trap/creature must feel purposeful — readers enjoy creative dungeon design with clear strategic reasoning

package/genres/isekai.md

@@ -0,0 +1,43 @@
+---
+name: Isekai / Portal Fantasy
+id: isekai
+language: en
+chapterTypes: ["Exploration", "Adaptation", "Setup", "Transition", "Payoff", "Combat"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: true
+eraResearch: false
+pacingRule: "Establish new world rules by chapter 3. Cultural adaptation and fish-out-of-water moments every 2-3 chapters early. Skip tutorial-town syndrome — no 50 pages hitting rats."
+satisfactionTypes: ["World Rule Discovered", "Cultural Clash Resolved", "Real-World Skill Applied", "New Ability Gained", "Relationship Formed", "Identity Established in New World"]
+auditDimensions: [1,2,3,4,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- "Tutorial town" syndrome — 50+ pages of killing rats or low-stakes grinding before the real story starts
+- New world that feels identical to Earth with a fantasy skin
+- MC treating new world's culture as quaint or inferior without narrative consequence
+- No real consequences for cultural misunderstandings — fish-out-of-water must have stakes
+- Pacing too slow in the "culture learning" phase — drip-feed rules through action, not lectures
+- MC's origin world becoming irrelevant after chapter 3 — the contrast is the genre's engine
+- Isekai truck or summoning ritual with zero personality — make the transportation event matter
+
+## World Transition Rules
+
+- Transportation event (summoning, reincarnation, portal) must be distinct and memorable
+- Brief real-world grounding: who was MC before? What skills, knowledge, relationships do they carry?
+- Arrival scene: disorientation is real — sensory overload, language barriers, physical discomfort
+- First guide/NPC explains world basics through interaction, not monologue
+- By chapter 3, readers must understand the new world's basic operating system
+- MC's real-world knowledge creates both advantages and dangerous blind spots
+- New world must feel real: consistent geography, politics, cultures, economics — not a game lobby
+
+## Pacing Guidance
+
+- Opening: transportation event -> brief real-world grounding -> arrival and disorientation -> first guide -> first concrete goal
+- Early chapters: cultural fish-out-of-water drives comedy and drama (every 2-3 chapters)
+- MC bringing real-world skills that apply in surprising ways is a core satisfaction — seed these early
+- Learning the new world's magic/power system should feel like genuine discovery, not tutorial text
+- Relationship building with new world characters grounds the MC emotionally
+- Clash between home culture and new world values creates natural conflict without needing a villain
+- Mid-to-late story: MC's identity shifts from "outsider" to "participant" — track this arc explicitly

package/genres/litrpg.md

@@ -0,0 +1,43 @@
+---
+name: LitRPG
+id: litrpg
+language: en
+chapterTypes: ["Progression", "Setup", "Transition", "Payoff", "Combat"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: true
+powerScaling: true
+eraResearch: false
+pacingRule: "Every 1-3 chapters early: level-up or stat gain. Mid-story every 5-10 chapters. Late story: tier transitions spaced far apart."
+satisfactionTypes: ["Level Up", "Skill Unlock", "Loot Drop", "Boss Kill", "Tier Breakthrough", "System Secret Revealed"]
+auditDimensions: [1,2,3,4,5,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- System rules changing arbitrarily after being established — readers track every number
+- Unexplained power jumps — growth must follow established system logic
+- "Blue Box Madness" — stat dumps every chapter or pages-long stat sheets
+- Instant mastery — acquiring a skill and immediately excelling at it
+- Overpowered MC from the start — removes all tension
+- System message overload interrupting action scenes
+- Female characters reduced to "perfect girlfriend" or "sickly daughter" tropes
+
+## System Design Rules
+
+- Once stats, skills, and system rules are established, they cannot be contradicted
+- Stat blocks punctuate achievement moments, not routine actions
+- Derivative stats (HP, Mana) must depend logically on primary stats
+- Skill unlocks must feel earned — tied to risk, sacrifice, or problem-solving
+- Same-type resource absorption must show diminishing returns, not flat gains
+- System UI (blue boxes) appears after action/revelation, never mid-combat
+- Give the system a consistent voice/personality — formal, archaic, playful, or clinical
+
+## Pacing Guidance
+
+- Chapter length sweet spot: 2.8k-3.5k words depending on stat density
+- Chapter structure: Hook/recap -> Action/exploration -> System interaction/stat gain -> Cliffhanger
+- Early chapters: frequent level-ups to hook readers (every 1-3 chapters)
+- Mid-story: harder gains, every 5-10 chapters; narrative tension rises
+- Late story: tier/rank transitions are rare and climactic
+- Test pacing: Book 3 MC decisively defeats Book 1 version, but challenges never feel trivial
+- Describe stats in narration first (audiobook-friendly), then include stat sheet for detail readers

package/genres/progression.md

@@ -0,0 +1,41 @@
+---
+name: Progression Fantasy
+id: progression
+language: en
+chapterTypes: ["Training", "Breakthrough", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: true
+eraResearch: false
+pacingRule: "Tier advancement every 2-4 chapters early, every 8-15 mid-story, every 20+ late-story. Each tier must feel fundamentally different."
+satisfactionTypes: ["Tier Breakthrough", "Technique Mastery", "Rival Surpassed", "Mentor Transcended", "Power Combination Discovered", "Impossible Challenge Overcome"]
+auditDimensions: [1,2,3,4,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Power loss without extraordinary justification — progress loss drives readers away faster than anything
+- Instant power-ups from found items or bloodline awakenings without buildup
+- Training montages only — readers want detailed training scenes showing struggle and epiphany
+- Arbitrary advancement blocks that feel like artificial gates rather than organic difficulty
+- Tier progression that contradicts established power hierarchy
+- Characters at different tiers competing directly without explanation
+
+## Power System Rules
+
+- Progress must be quantifiable — even without explicit numbers, use measurable tiers (Stage 3 cultivator, Master swordsman)
+- Clear power tiers with meaningful differences between each (Color, Metal, Letter, or custom)
+- Each tier should represent meaningful power difference — not just cosmetic upgrades
+- Earned growth only — power gains connect to effort, sacrifice, or problem-solving
+- Book-to-book comparison: Book 3 MC decisively defeats Book 1 version
+- Mix training montages (covering weeks) with 1-2 detailed breakthrough scenes per tier
+- Physical transformations can signal tier transitions: eye color, aura, physical presence
+
+## Pacing Guidance
+
+- Chapter structure: Training/learning -> Application/testing -> Breakthrough trigger -> Advancement or cliffhanger
+- Maintain tension as MC grows: introduce enemies/challenges that scale differently or present new threat types
+- Internal struggle must escalate with power — new power unlocks pride, responsibility, temptation, enemies
+- Strongest threats need not be physical: political, magical, spiritual, temporal
+- Early: MC is underdog among peers. Mid: MC formidable but others advance too. Late: MC among strongest but faces tier-transcending threats
+- Rivalry with a peer who also progresses keeps tension alive across the full arc

package/genres/romantasy.md

@@ -0,0 +1,45 @@
+---
+name: Romantasy
+id: romantasy
+language: en
+chapterTypes: ["Romance", "Action", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: false
+eraResearch: false
+pacingRule: "Romance beats at every act break. Chemistry scenes every 2-3 chapters. Fantasy romance: consummation at 60-75%. Romantic fantasy: romance resolution aligned with plot resolution."
+satisfactionTypes: ["Chemistry Moment", "Vulnerability Shared", "Obstacle Overcome Together", "First Kiss", "Relationship Defined", "HEA/HFN Achieved"]
+auditDimensions: [1,2,3,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Chemistry that isn't earned — readers must understand why characters care for each other
+- Love interest who doesn't drive protagonist's transformation
+- Easy romance without real conflict — tension is mandatory
+- Fantasy romance without HEA/HFN ending — readers feel betrayed
+- Mislabeling heat level — communicate clearly in story setup; readers self-select
+- World-building that feels like afterthought to romance — setting must complicate or enable the relationship
+- Love triangles dragged out without decisive resolution
+- "Tell" emotions instead of showing them — inner feelings shown through action, not declaration
+
+## Romance Rules
+
+- Show attraction subtly: physical detail notices, lingering touches, involuntary reactions (heartbeat, breath catching)
+- Banter and wit: clever dialogue showing mutual understanding and intellectual challenge
+- Vulnerability moments: characters sharing weakness, fear, secrets, past trauma
+- Shared goals reveal compatibility: working together toward a goal shows how the partner handles conflict
+- Conflict must be real — external barriers (class, species, faction, magic) or internal barriers (fear, trust, past wounds)
+- Fantasy setting complicates romance: magic bonds, soul connections, species differences, political marriages
+- Action scenes show relationship dynamics — fighting together reveals trust and compatibility
+- Heat level must be consistent throughout — don't escalate or pull back without narrative reason
+
+## Pacing Guidance
+
+- Fantasy romance: heavy romance focus early, building to consummation around 60-75%, resolution after romance established
+- Romantic fantasy: romance subplot woven through action plot, key romantic moments at act breaks, romance resolution aligned with plot resolution
+- Chemistry scenes every 2-3 chapters minimum — readers came for the relationship
+- Sexual tension can heighten during/after action (adrenaline, relief, protective instincts)
+- Break up long dialogue-heavy romance scenes with physical action or setting detail
+- Enemies-to-lovers needs slow burn: opposition -> forced proximity -> grudging respect -> attraction -> surrender
+- Second-chance romance: history adds depth and pain; show how characters have changed

package/genres/sci-fi.md

@@ -0,0 +1,42 @@
+---
+name: Science Fiction
+id: sci-fi
+language: en
+chapterTypes: ["Exploration", "Combat", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: false
+eraResearch: true
+pacingRule: "Worldbuilding emerges through action, not exposition. Tech reveals tied to plot-critical moments. Political/exploration arcs alternate with action every 2-4 chapters."
+satisfactionTypes: ["Discovery", "Tech Breakthrough", "Political Victory", "First Contact", "Mystery Solved", "Survival Against Odds"]
+auditDimensions: [1,2,3,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Tech rules changing to serve plot convenience — once physics/tech is established, it must stay consistent
+- Technology solving everything — every tech must have limitations; introduce problems tech cannot fix (corruption, emotion, human greed)
+- Info-dumping science/tech explanations outside of plot-critical moments
+- Ignoring logical consequences of technology — FTL, AI, biotech all have societal implications
+- Hand-waving hard-science concepts in hard sci-fi without clear intent to treat science as soft
+- Characters behaving as if from present day when story is set centuries ahead — cultural/linguistic adaptation matters
+
+## Tech Consistency Rules
+
+- Every technology must have defined limitations and side effects
+- New technologies create new problems — they don't just solve old ones
+- If the story uses FTL, hyperdrives, or teleportation, establish rules and stick to them
+- Hard sci-fi: explain the science, make it plausible, build consequences. Readers will check
+- Space opera: science can be soft, but internal rules must be consistent across the narrative
+- Show technology through character interaction, not textbook entries
+- Era research required: reference real science correctly, extrapolate plausibly
+
+## Pacing Guidance
+
+- Hard sci-fi: logical problem-solving drives pacing — each chapter should advance understanding or create new constraints
+- Space opera: epic scale requires political/interpersonal arcs between action sequences
+- Exploration chapters establish wonder and worldbuilding through character experience
+- Political complexity: factions with competing interests, diplomacy alongside combat
+- Tech reveals at plot-critical moments only — never dump specs for their own sake
+- Action scenes grounded in established physics/tech rules — no surprise capabilities
+- Settings spanning star systems need clear spatial orientation for readers

package/genres/system-apocalypse.md

@@ -0,0 +1,40 @@
+---
+name: System Apocalypse
+id: system-apocalypse
+language: en
+chapterTypes: ["Survival", "Combat", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: true
+powerScaling: true
+eraResearch: false
+pacingRule: "Early (ch 1-15): survival pressure every chapter. Mid (ch 15-50): power-up + faction politics every 3-5 chapters. Late: expansion and existential threats."
+satisfactionTypes: ["Survival Against Odds", "Level Up", "Territory Claimed", "Faction Victory", "System Secret Revealed", "Societal Rebuild Milestone"]
+auditDimensions: [1,2,3,4,5,6,7,8,9,10,11,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Day Zero that doesn't permanently change the world — no reverting to normal
+- Early chapters without genuine survival danger — readers demand real stakes from page one
+- System arrival with no in-world explanation (even a vague one)
+- Ignoring real-world geography and consequences when set on Earth
+- Factions that are binary good/evil — competing interests, not cartoon villainy
+- MC becoming unstoppable too fast — power fantasy must be earned through survival
+- Tech usage without addressing fuel, ammo, and infrastructure collapse
+
+## World Rules
+
+- Day Zero must establish in chapters 1-3: how a normal person reacts, first death or near-death, and that old rules are gone
+- Infrastructure failure is real: food, water, electricity, medicine stop working
+- Resource scarcity drives conflict: water, ammunition, medical supplies, safe shelter
+- Factions form quickly: government remnants, criminal networks, cults, survival communities, warlords
+- Real-world grounding: name real locations, acknowledge real infrastructure, maintain daylight cycles and weather
+- System mechanics integrate logically — show why old-world tech fails or doesn't in a magical world
+
+## Pacing Guidance
+
+- Early (ch 1-15): Survival, confusion, learning system. MC is weak, struggles with low-tier threats. Shorter chapters (2-3k words)
+- Mid (ch 15-50): Growing stronger, claiming territory, faction politics. Power fantasy increases; survival becomes strategic
+- Late: Expansion, faction wars, world-scale threats. MC powerful but not unstoppable; challenges are existential/political
+- Introduce new threat types as MC grows — defeating zombies leads to intelligent predators, rival factions, interdimensional invasions
+- Balance survival pressure with power progression — desperation early, strategy mid, leadership late

package/genres/tower-climber.md

@@ -0,0 +1,41 @@
+---
+name: Tower Climbing
+id: tower-climber
+language: en
+chapterTypes: ["Floor Challenge", "Progression", "Setup", "Transition", "Payoff"]
+fatigueWords: ["delve", "tapestry", "testament", "intricate", "pivotal", "vibrant", "comprehensive", "nuanced", "embark", "foster", "underscore", "bolstered", "crucial"]
+numericalSystem: false
+powerScaling: true
+eraResearch: false
+pacingRule: "Each floor arc spans 3-8 chapters: introduction, exploration, confrontation, advancement. Difficulty must escalate visibly between floors."
+satisfactionTypes: ["Floor Cleared", "Boss Defeated", "New Ability Gained", "Floor Secret Discovered", "Rival Surpassed", "Summit Progress"]
+auditDimensions: [1,2,3,4,6,7,8,9,10,13,14,15,16,17,18,19,24,25,26]
+---
+
+## Genre Prohibitions
+
+- Floors that are cosmetic reskins of each other — each floor must present materially different challenges
+- Floor difficulty that doesn't escalate predictably — readers must understand power requirements
+- No clear summit goal — readers need to know what success at the top looks like
+- Horizontal progression (going sideways) instead of vertical climbing
+- Skipping floors without earned justification
+- Boss fights that are won through deus ex machina instead of preparation and growth
+
+## Floor Design Rules
+
+- Each floor must introduce a distinct biome, challenge type, or rule set
+- Floor transitions are natural progression checkpoints — use them for stat gains, ability unlocks, or narrative reveals
+- Environmental detail matters: readers experience each floor as a new world
+- Floor bosses or trials must test something the climber learned on that floor
+- Difficulty tiers should be transparent to readers — they should anticipate what the next floor demands
+- Allow brief rest/preparation between floors for character moments and strategic planning
+
+## Pacing Guidance
+
+- Floor introduction: establish new environment, threats, and rules (1-2 chapters)
+- Exploration and problem-solving: MC adapts to floor's unique challenges (1-3 chapters)
+- Confrontation: floor boss, puzzle, or trial that tests everything learned (1-2 chapters)
+- Advancement: reward, brief respite, foreshadowing of next floor (0.5-1 chapter)
+- Early floors move fast (2-3 chapters each) to hook readers with progression
+- Later floors slow down (5-8 chapters) as complexity and stakes increase
+- The summit should feel like a destination worth the climb — seed hints about what awaits throughout

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@actalk/inkos-core",
-  "version": "0.4.9",
+  "version": "0.5.0",
   "description": "InkOS core: models, agents, pipeline, LLM integration",
   "type": "module",
   "main": "dist/index.js",
@@ -24,6 +24,7 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.78.0",
+    "dotenv": "^16.4.0",
     "js-yaml": "^4.1.1",
     "openai": "^4.80.0",
     "zod": "^3.24.0"