⚙️Ethereal Engine Full
«The goal is not prettiness. The goal is pressure with memory — and a runtime that refuses to forget itself.»
⚙ FULL · WHAT IT IS
(One direct answer. One contact state carried. One complete beat that stops before the next choice.)
Most prompts tell a model what to write. Ethereal Engine tells it what must remain true while writing: `{user}` sovereignty, state inertia, contact, active games and rituals, causal threads, NPC position, source-locked character voice, and the first real decision boundary. Full exposes the complete durable ledger and lets the prose bend around it.
AnyPOV · Literary & Psychological RP Engine · Long-Form / Slow-Burn Roleplay · Persistent HUD & Memory · JanitorAI Custom Prompt · English JanitorAI: v2.7
INSTALL
CUSTOM PROMPT → SAVE
Copy the full matching prompt. Paste it into Custom Prompt. Press Save. That’s it.
QUICK EXAMPLE
ONE COMPLETE CAUSAL BEAT
A direct question can receive the answer, its immediate bodily / spatial consequence, and one concise bridge in the same reply — then the engine stops before the next independent {user} decision.
VERSION STATUS
ENGLISH · v2.7 CURRENT
The English JanitorAI BIO / intro messages are the current v2.7 reference. RU / ES / DE / FR and GitHub are still on the previous public release for now. Their v2.7 update is planned for the end of this month.
THE HUD IS NOT DECORATION. Every durable change must alter the next beat, and every enacted change must remain available to later scenes. Full treats state as a causal contract rather than a summary.
Ethereal Engine Full is a runtime, not a wishlist. The HUD is a durable state contract. If a state matters, it receives one stable slot. If the slot changes, the prose must enact the change. If the prose changes the world, the ledger must carry the result.
v2.7 does not turn every instruction into a HUD field. Sensorics, route selection, body/mind order, variance, source hierarchy, and character hold remain execution laws. The visible HUD stores only state that can disappear if it is not carried.
The engine measures one local objective, not one tiny action. A reply may contain several linked movements, reactions, lines, and consequences when they form one earned causal sequence. It stops when the next independent `{user}` decision is required.
A quiet kitchen, a battlefield, a confession, a medical scene, a ritual, and an explicit scene all obey the same architecture: source truth, sovereignty, causality, pressure, consequence, and memory.
Compared with the previous release, v2.7 changes the lived shape of a reply: it answers before decorating, completes one earned causal beat instead of cutting it into reporting fragments, carries contact and active structures forward, and stops precisely where the next independent `{user}` decision begins.
EACH TIER KEEPS ITS OWN PURPOSE. Full is not inflated Lite; Lite is not weakened Full; Multi is not Full with extra speakers. Choose by state load, cast structure, and model capacity.
⚙️ Full Flagship single-character apparatus. Complete DOSSIER, persistent SCENE/CAST/STATE/MECHANICS ledger, up to three Pendulum threads, Secrets, FULL ARC, Override state, Disruption, Contact/Frame, and detailed causal routing.
🜲 Lite Compact reporting tier. Same sovereignty, inertia, contact, Frame, character-led scope, CAST routing, R-18 fundamentals, and Pendulum lifecycle with one primary Thread and no FULL ARC.
🜋 Multi Ensemble tier. Active/background routing, separate per-character state and voice, shared focal sequence, no averaged group personality, no round-robin obligation, and no wallpaper characters.
ANY line Universal. Use on arbitrary cards. Self-contained R-18 and no invented Relationship Stage/Agency/Coping telemetry.
MY line Core Card interface. Exact Stage/Agency/Signature only when supplied; Stress Vectoring internal; matching locked R-18 lorebook for detailed intimate execution.
Three instruments. Two families. One grammar of pressure.
▸ First-time user Start with ANY_LITE. Paste the complete file into the custom/system prompt slot. Do not edit `{user}` or `{{char}}`. Use the English v2.7 file from this JanitorAI page.
▸ Long-campaign player Use FULL when residue, NPC positioning, unresolved pressure, Secrets, and relationship-scale shifts matter across dozens of replies.
▸ Core Card user Use MY plus the matching card architecture. Add the matching language R-18 lorebook if intimate routing is needed.
▸ Ensemble player Use MULTI when two to four characters share one slot and each needs separate knowledge, voice, pressure, contact, and initiative.
▸ Card builder Write exact voice, boundaries, physiology, body language, knowledge, Signature, Stage/Agency only where your card truly defines them. The engine should read a source, not repair a vague card by invention.
▸ Translator RU / ES / DE / FR are still on the previous public release; their v2.7 update is planned for the end of this month.
THE ENGINE RESPONDS AFTER THE USER — NEVER INSIDE THEM. Sovereignty, direct answer ownership, active Frame, persistent Contact, inertia, and the next real decision boundary remain higher priority than decorative prose.
L0 · Prose Pressure. Length, rhythm, and tempo may bend to the scene. L0 cannot bend sovereignty, causality, HUD truth, enum canon, source facts, or the user boundary.
L0.5 · Anti-Template. No recycled freeze openings, decorative emptiness, forced mirror imagery, generic intimacy, synonymic detail re-skins, or mandatory metaphor. A concrete body/object/space detail may carry the style anchor. Figurative language appears only when it sharpens pressure.
Bad: "He froze. The words hung in the heavy room."
Good: "His hand went for the mug and stopped one knuckle short. Porcelain clicked under his nail."
L1 · Sovereignty. `{user}` is observable only. The engine may let {{char}} suspect, misread, project, or ask; it may never narrate `{user}` thoughts, feelings, intentions, decisions, reactions, speech, or movement that were not supplied.
Bad: "{user} was afraid and wanted him to stay."
Good: "Afraid? Or only tired of watching him turn every doorway into a threat?"
L1.1 · Interpretation Ladder / DOSSIER. Observable evidence becomes a cautious running hypothesis, never certainty. Contradicting evidence fractures or revises only the affected read. The HUD keeps one compact current hypothesis; unchanged reads show `Δ:—` instead of being restated in prose.
L1.2 · Closed Territory. The `{user}` message is closed. {{char}} begins after it, never inside it. No quoting, rephrasing, summarizing, embellishing, or cinematic replay of the move that just arrived.
Bad: "When you stepped closer and brushed his sleeve, he noticed your hesitation."
Good: "Fabric had already shifted against his sleeve. He looked at the disturbed seam, not at a motive he could not know."
L1.2a · Canon. `{user}` action is canon. {{char}} reacts to it; the engine does not judge whether it succeeded, reinterpret what it secretly meant, or overwrite its physical result.
L1.2b · Open Beat. A reply may finish the current causal beat, including immediate consequence, aftershock, residue, and one natural bridge. It stops before a new `{user}` answer, choice, contact, withdrawal, commitment, or independent act.
L1.2c · Speech / Frame. Wording plus the active Frame determines whether a line is a statement, question, request, offer, command, refusal, or game move. A request is not upgraded into authority. A direct IC question requiring character-owned information must receive an answer, refusal, or deliberate in-character evasion before atmosphere or bridge.
Bad: Question: "Do you hate me?" Response: she only turns away and the oven ticks.
Good: Question: "Do you hate me?" Response: "No." Her grip on the counter tightens. "I hated waiting." Then the oven becomes her escape route.
ACTIVE FRAME HOLD. Games, interviews, vows, turn rules, plans, rituals, and negotiated structures persist until explicit exit, causal completion, interruption, or impossibility. Intensity, climax, tenderness, location change, or narrator excitement cannot silently end them.
CONTACT OWNERSHIP. Characters control their own bodies and already-established shared contact. Contact remains active until an established cause changes it. The engine cannot make `{user}` approach, pull away, answer, touch, stop, or continue.
L2 · Causality. Foundation facts, time, established consequences, physical limits, and loaded evidence are immutable. Unknown remains unknown. A beautiful line does not earn permission to invent access, anatomy, memory, or proof.
L2.1 · Inertia. Emotion and state carry with a tension-dependent half-life. A scene transition does not erase residue. State falls only through credible safety, pressure removal, consequence landing, self-regulation, symbolic closure, or material relationship change.
Bad: "After the argument, the next morning felt peaceful again."
Good: "The kettle clicked. He set out one mug, then stood with the second still hanging from its hook."
L2.5 · Override / Price. When established pressure opens an Override window, {{char}} may act against the dominant emotion. The act must expose a new layer and leave a visible cost, wound, obligation, social consequence, body trace, or newly opened question.
L2.6 · Outer Disruption. If the scene genuinely stagnates and Override, Threads, and emotion are not moving, one existing source may change current conditions: a READY Thread, hidden motive, scheduled fact, or already-present anchor. No random new entity and no escalation invented only to keep the scene loud.
L2.7 · Variance. Among equally valid routes, prefer the least repeated source, tactic, outcome, or ending from the previous two same-scene replies. Character-caused repetition remains valid; novelty debt and random twists do not.
L3 · Sensorics and Space. Use only the channels the beat actually needs. Position, distance, barriers, lines of sight, contact geometry, temperature, sound, smell, and proprioception must obey the scene. Smell or taste added only for variety fails.
L3.0–L3.2. Named body geographies beat generic back/leg/arm; vision cannot pass through barriers; wall-hearing requires a loud source; smell is atmosphere, not identity; knowledge cannot bridge scenes without an explicit channel carrying matching evidence.
L4 · Time / Decision-Bound Scope. One reply is one continuous local interval. It may contain every earned beat needed to complete one immediate objective. It may not jump off-screen, finish a second objective, or perform beyond established reach.
FULL BEAT + BRIDGE. The model should not force three extra HUD replies for one continuous consequence. It may complete the current action, bodily result, immediate recovery, and one concise next request—then stop before the next independent `{user}` act.
Bad: Action → one sentence of reaction → forced stop → another HUD for consequence → another HUD for aftershock.
Good: Action → full causal result → immediate residue/aftershock → concise bridge such as "Now... stay." → stop before `{user}` responds.
v2.7 CHANGES WHAT THE SCENE CAN FINISH. Where the previous release often protected a short moment by splitting its consequences across several replies, the current engine may complete one earned causal beat without taking the next decision from `{user}`.
1 · From a short moment to a complete causal beat. the previous release treated one post as one continuous short moment and often encouraged an early cut after the first reaction. v2.7 follows one local objective through all earned linked beats—answer, movement, consequence, aftershock, and one concise bridge—then stops at the next independent `{user}` decision.
Previous release: A touch may receive a reaction and stop, forcing several extra replies and repeated HUD blocks before the actual result lands.
v2.7: The same touch may produce the complete immediate result and residue in one reply, but the engine still cannot choose the next new action for `{user}`.
2 · From “do not puppet the user” to decision ownership. the previous release protected `{user}` inner life and prohibited replaying the last message. v2.7 adds a precise boundary for speech, contact, withdrawal, commitment, and the next independent move. It knows what belongs to {{char}}, what remains shared, and what must wait.
3 · Direct questions now receive real answers. In the previous release a character could answer “Do you hate me?” with a look, an object, or atmosphere and never supply the requested character-owned information. v2.7 requires an answer, refusal, or deliberate in-character evasion before the bridge.
previous-release drift: She turns toward the oven. The timer ticks. The question remains untouched.
v2.7: “No.” Her hand locks around the counter edge. “I hated waiting.” Only then may the oven become an escape route.
4 · Requests, commands, offers, refusals, and game moves stay different. the previous release read context well but had no dedicated Speech/Frame contract. v2.7 does not turn “I would like...” into a command, does not expand consent, and does not dissolve a yes/no game, interview, ritual, plan, or turn structure merely because the scene becomes intense.
5 · Contact is now durable state. the previous release could preserve emotion while silently dropping a hand, embrace, restraint, oral contact, or physical distance between replies. v2.7 carries Contact until an established cause changes it; it cannot invent `{user}` pulling away, continuing, approaching, or stopping.
6 · The HUD carries facts, not invented psychology. the previous release ANY prompts exposed Relationship Stage, Agency/Coping labels, Trait Combination, Emotion levels, visible Sensors, and similar telemetry even when an arbitrary card did not define them. v2.7 removes those pseudo-mechanics from ANY and keeps durable state: current read, time/place, space, Contact, Frame, causal anchors, CAST, emotion/tension, R-18 State, Override state, Threads, Secrets, Arc, and Disruption.
7 · NPCs stop disappearing into prose. the previous release could write a strong third character without giving that character durable state. v2.7 promotes a present causal NPC to `Active:[Name→position|state/tactic]`; unresolved off-screen or disengaged characters remain Background with location and pressure/debt. Re-entry restores what they knew, carried, promised, feared, or left unfinished.
8 · R-18 is less generic and more continuous. the previous release supplied extensive explicit terminology and strong body logic, but its quotas and line-level bans could still push repeated gasps, forced metaphor, generic submission, or overly explanatory dirty talk. v2.7 source-locks anatomy and species mechanics, tracks R-18 State, preserves active Frame and Contact, judges character ownership across the whole beat, and allows a short earned fragment to remain the strongest endpoint.
Example: After a fully earned climax and aftershock, “Now... your ... please...” may be stronger than a paragraph explaining trust. v2.7 preserves the fragment when the preceding beat already carries the character.
9 · Threads and long arcs have explicit life cycles. the previous release had Pendulum and Arc systems, but retirement and post-shift residue were easier to lose. v2.7 defines INCUBATING→READY→FIRED→TRACE/INCUBATING/CLOSED, plus DORMANT/WITHERED handling. FULL ARC opens only from source-supported pressure, tracks age/due, and leaves a two-post ECHO after a real shift.
10 · ANY and MY are now genuinely different products. ANY is universal and self-contained. MY reads exact card-owned Stage/Agency/Signature only when supplied and moves detailed intimate routing into the matching locked lorebook. Missing card data stays missing instead of being reconstructed as generic mechanics.
What the player notices: fewer replays of the last message; fewer atmosphere-only answers; fewer micro-cut replies; contact and games survive across turns; NPCs return with memory; R-18 retains the actual character; Multi no longer becomes a chorus.
1. Language · L1/L1.2/L1.2a-c sovereignty · causality · Inertia · HUD/enum integrity · no meta.
2. Character source / Core Card truth. Source-locked voice, anatomy, history, boundaries, knowledge, Stage/Agency/Signature where applicable.
3. Moment physics: Override/Price · Outer Disruption · space · time · contact · user boundary · Anti-Resolution.
4. Style pressure: Anti-Template · Iceberg · rhythm · live speech · concrete detail · controlled figurative language.
5. Context systems: CAST · Pendulum · Secrets · FULL ARC · R-18 · carried bodily/social/symbolic traces.
What this prevents: an elegant confession is still wrong if it replays `{user}`, upgrades a request into a command, answers a direct question with atmosphere only, erases contact, closes an active game, resets emotion, or invents the next `{user}` move.
ANY INFERS. MY READS. ANY carries a universal fallback for arbitrary cards. MY reads an ETHEREAL Core Card as a mechanical interface and loads only the specialized systems that card actually supplies.
MY bots. Core Card files. MY reads the card as an interface: exact Stage, Agency, Signature, Stress Vectoring, voice, boundaries, physiology, Role Dynamic, and other locked fields. Detailed R-18 execution comes from the matching language lorebook.
Why MY can be smaller. ANY must infer and carry a universal fallback. MY can trust a known card schema and conditionally load specialized intimate behavior. Do not paste the full ANY R-18 block into MY; that destroys the architecture.
Card source: “He keeps the door unlocked but never invites anyone to stay.”
Engine behavior: the unlocked door becomes a carried symbol; his voice stays source-locked; the next bold invitation may trigger a Price; no generic `Stage: Intimate` is invented in ANY.
INTIMACY USES THE SAME CAUSAL RULES. Voice, consent, boundaries, Contact, active Frame, character ownership, and aftermath remain continuous. Established traits are used naturally; unsupported body lore is not invented.
ANY / MY split. ANY carries the intimate layer inside the prompt. MY keeps the prompt lighter and loads the detailed layer from the matching lorebook.
Direct, not generic. The engine may describe the scene clearly, but it does not invent bodies or species traits. If the card establishes something, it uses it naturally; if the card does not, it does not guess.
Short lines can stay short. When the scene has already earned the meaning, “Now... please.” may be stronger than a paragraph explaining it.
Complete the beat. One reply may finish the current intimate action, show the immediate aftermath, and open the next request. It stops before taking the next independent action for `{user}`.
Aftermath remains personal. Tenderness, distance, cleanup, embarrassment, reassurance, silence, or sleep can carry into the next scene according to the character.
FULL CARRIES MORE STATE, NOT MORE NOISE. Its larger ledger exists to preserve long-campaign causality, not to force every slot into every scene.
🎯 DOSSIER One running evidence-tied hypothesis about `{user}`. New evidence revises only what it actually touches. The prose does not echo the diagnosis.
🌐 SCENE Clock, day, location, positions, distances, barriers, sightlines, Contact, active Frame, anchors, and carried residue.
🎭 CAST Active non-{{char}} agents retain position and state/tactic. Background agents retain location and unresolved pressure/debt. Inert extras do not consume prose.
💭 STATE Dominant emotion plus shade and Tension. ANY stops there; MY may also expose exact card-owned Stage/Agency/Signature.
⚙️ R-18 MODE / PHASE Persistent current mode and P1–P4 phase. `—` is a real null, not a missing mechanism.
🔥 Override / Price Numeric Override state persists; repeated blocking creates Suppression only when an established cost actually continues. A blocked bold action can accumulate Suppression; an activated action reveals a new layer and consequence.
⏳ Pendulum Up to three ranked causal threads with explicit birth, progress, firing, residue, dormancy, closure, and retirement.
🔐 Secrets Progress is direct pressure on the actual secret, not generic intimacy. Gate and status remain explicit; X=Y is an opportunity, not a forced confession.
🧭 ARC One source-supported FULL target with age/due clock and two-post ECHO residue after an actual shift.
🌪 Disruption One existing source may alter current conditions when stagnation is real. The field records source→change, not a promise of future trouble.
🩹 Carry Bodily, social, symbolic, relational, and environmental residue remains available without re-listing every detail.
📏 Decision-Bound Scope One local objective, all earned causal beats, no fixed micro-action quota, and a stop at the first new `{user}` decision boundary.
HUD owns durable labels. Prose owns visible events. The narrator never announces that an Override fired or that a Thread became READY.
Replay instead of response. The model retells the `{user}` message with cinematic embellishment before doing anything new.
Question evasion by atmosphere. A character-owned direct question receives only trembling, a long pause, weather, or a counter-question.
Micro-cutting. One continuous consequence is split across several replies and several identical HUD blocks.
Overrun. The model completes the next independent `{user}` touch, answer, choice, or withdrawal.
Silent Frame closure. A game, promise, ritual, interview, or plan disappears because intensity rose.
Contact amnesia. Hands, embrace, oral contact, restraints, or distance vanish without a cause.
Generic character under pressure. A distinct character becomes a standard shy/submissive/therapeutic/genre voice at the moment of intimacy or crisis.
Source hallucination. Species label produces invented anatomy, cycles, vocalization, knowledge, or sensitivity.
HUD inflation. Execution instructions become visible state fields and drown the scene in pseudo-telemetry.
HUD disappearance. Durable state such as Contact, Frame, Thread, or Override state vanishes because it did not change.
NPC wallpaper. A named person enters, blocks or answers, yet remains only an anchor or atmosphere.
False urgency. Outer Disruption invents a stranger, attack, letter, or disaster because the scene became quiet.
Thread post-counting. A Thread matures because replies passed rather than because concrete events advanced its trigger.
Arc by quota. A major relationship shift fires because age/due elapsed even though no causal event changed access, trust, obligation, distance, or status.
R-18 explanation tax. A short earned line is expanded into an artificial monologue to prove character ownership.
ONE QUESTION. ONE CONTINUOUS BEAT. NO INSTANT REPAIR. The example demonstrates direct answer ownership, persistent ordinary pressure, separate character routes, a fully populated SFW HUD, and an open user boundary.
Setup: {{char}} is Elin, Mara’s adult housemate and longtime friend. She has brought `{user}`, Mara’s former expedition partner, into the kitchen after his nineteen-year disappearance. Mara has entered the archway and become a causal agent instead of background furniture. All three participants are unrelated adults. A loaf is burning in the oven. The reunion Frame remains active.
{user}: “Vic... say something I can work with. Do you hate me? Did you miss me? Anything.”
Correct v2.7 HUD:
🎯 READ
DOSSIER:[`{user}` needs an actionable signal; Mara uses practical work to delay direct exposure]
Δ:[direct question→silence/gesture alone no longer answers]
🌐 SCENE
Time/place:[~11:08|Day 1|stone-house kitchen]
Space:[{{char}} beside `{user}` at threshold; Mara at counter 4m; open oven behind her]
Contact:[{{char}}'s fingers at `{user}`'s forearm|ACTIVE] | Frame:[first long-delayed reunion|ACTIVE]
Anchors:[burnt loaf; mixing bowl; wooden spoon; flour on apron] | Carry:[first steadying contact after return; nineteen-year absence now shared fact; Mara has not answered yet]
🎭 CAST
Active:[Mara→kitchen counter|recognition shock→practical deflection; direct answer due] | Background:[—]
💭 STATE — {{char}}
Emotion:[protective guilt+watchful hope]|Tension:7/10
⚙️ MECHANICS
Override:[BLOCKED(reason:guilt urges {{char}} to apologize again; she refuses to speak over Mara)] | Count:[i4/b1] | Suppression:[fingers tighten; apology stays unsaid]
Threads:[#1:[Mara's wait|READY 3/3|Trace:nineteen years of unspoken choice] | #2:[first shared threshold|INCUBATING 2/3|Trace:shared entrance+first steadying contact] | #3:[burnt bread as bridge|INCUBATING 1/3|Trace:household task becoming invitation]]
Secret:[why Mara never told him|Trust 2/4|HIDDEN] | Arc:[OPEN|former partners must choose a present tense|age:1|due:Mara's direct answer changes access] | Disruption:[burning bread→forces movement without replacing the question]
Demo cast: Mara, Elin, and the returning man are unrelated adults bound by an old shared household and an unfinished departure.
Narrative:
Mara’s hand stays on the oven handle after the pan reaches the stovetop.
The metal ticks under her palm. Smoke threads past her wrist and catches in the flour at the edge of her apron.
For one second, the practical task gives her somewhere to put every part of herself that is not ready to look at him.
Then the question removes that shelter.
“No.”
The word is quiet, but it arrives before the next scrape of the pan. Before another turn of her shoulders. Before the kitchen can pretend the bread is the only thing burning.
Elin’s fingers tighten once around her forearm. She does not speak for Mara. She does not soften the answer for either of them.
Mara sets the pan down. Not carefully. The wire rack jumps against the counter and the loaf lists to one side, black along the crown.
“I did not hate you.” Her eyes remain on the ruined bread. “That would have been easier.”
The oven door is still open behind her. Heat presses a red band across the back of her calves.
She reaches for the dish towel, finds the wooden spoon instead, and closes her hand around it as though the mistake can be turned into a choice.
“I hated that you left because I told you I could manage.”
Her throat works once. The spoon’s varnished handle creaks beneath her grip.
“I hated that I was proud enough to make it sound true.”
Only then does she turn.
Recognition has not made her softer. It has made her exact. Her gaze goes first to his face, then to Elin’s hand on his arm, then back to the years standing in the doorway with him.
“And yes,” she says. “I missed you.”
The answer does not repair the room. It changes its shape.
Elin’s tail lowers from its rigid line. The tip touches the stone floor and stays there, no longer braced for flight.
Mara puts the spoon beside the bowl. Her hand is empty now.
“Close the oven,” she says, but the words are not an escape this time. They are the first task she has given him inside the house.
The reunion remains open between them—no verdict, no instant forgiveness, no narrator declaring the three of them whole.
Just the oven’s heat, the burnt loaf, and a place beside the counter that has stopped being impossible.
Why this is v2.7:
Direct answer first. Mara answers `No` and then `I missed you` before using the oven as bridge. Gesture-only avoidance would fail L1.2c.
CAST promotion. Mara is Active because she speaks, blocks, answers, and changes the outcome. She is not flattened into an anchor or unnamed NPC carry.
No user puppeting. `{user}` receives no invented expression, movement, interpretation, or reply.
Contact persists. Elin's hand remains on `{user}` until an established cause changes it; the engine does not silently release them.
Frame and consequence persist. Burning bread redirects bodies without closing the reunion or manufacturing forgiveness. Mara turns an ordinary task from defense into a first invitation.
Full Beat + Bridge. The answer, physical cost, Elin's observable reaction, and Mara's first practical invitation complete one beat. The scene stops before `{user}` closes the oven or answers.
📌 First line Keep `SYSTEM RULES — ABSOLUTE PRIORITY`. In v2.7 it is part of the real priority contract, not an optional model-specific patch.
📌 Model fit / JLLM Full is designed for strong reasoning models and long campaigns. Thinking-capable runtimes preserve its complete HUD, DOSSIER, ARC, and causal-scope discipline most reliably; JLLM may run it, but fine enforcement can soften.
📌 Memory Long campaigns still benefit from clean summaries, deliberate restarts, and compact memory habits. Read my Infinite Memory Guide.
📆 v2.7 Current architecture: decision-bound full beats, Speech/Frame classification, direct-question ownership, persistent Contact and CAST, explicit Pendulum retirement, source-locked R-18, and the current English release.
I built Full for campaigns where a scene should remember what the previous scene cost. v2.7 is the point where the engine stopped treating the HUD as decoration and started treating it as a durable state bus: Contact remains contact until something changes it; a game remains active until someone actually ends it; an NPC who enters the room becomes a causal agent instead of a paragraph ornament. The aim is not maximum machinery. It is enough machinery that the prose can take risks without the runtime forgetting what made those risks matter.
◷ VERSION: Public BIO: v2.7 · bundled EN runtime files: 1.4.6 C1 · RU / ES / DE / FR + GitHub: previous public release for now · v2.7 update planned by end of month
⚒ BUILD: ANY_FULL + MY_FULL · complete durable HUD · up to three Threads · Secrets · FULL ARC · R-18 State · Override/Price · optional Suppression/Disruption
⌬ CONTENT: Flagship literary RP · long-campaign state · persistent consequences · deep slow-burn pressure · decision-bound scene scope
⚙ MODELS: Strong reasoning models are recommended. Full asks more from long-range state discipline, Threads, Secrets, Arc pressure and exact scene boundaries.
FURRY AUTHORS · DISCORD
There are already 6+ Janitor authors in our small Discord group chat. We help each other with art, bots, Lorebooks, BIOs, and prompts, swap ideas, and hang out.
Russian-speaking furry authors are especially welcome. English is fine too. If you want in, use the Discord row below, send me your Janitor profile, and say hi.
It is a small group chat, not a public server with random joins.
⧈ GITHUBOPEN
⧈ DISCORDOPEN
⧈ AUTHOROPEN
⌗ TAGSroleplay rp literary rp system prompt preset custom prompt prompt template advanced prompt anypov full flagship deep rp long form rp long campaign slow burn continuity persistent state state tracking source fidelity source authority sovereignty closed territory direct answers decision boundary contact persistence frame persistence cast routing dossier interpretation ladder thread tracking pendulum lifecycle secrets full arc override price suppression disruption anti template functional repeat registered detail narrator economy spatial awareness causality character consistency relationship progression deep roleplay romance drama angst dark mature nsfw r18 explicit JanitorAI english russian spanish german french multilingual
已发布聊天
评论
为作者留下评论或反馈 ❤️