Instructions to use NovaCorp/Novaciano.Requiem-3.2-1B with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use NovaCorp/Novaciano.Requiem-3.2-1B with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="NovaCorp/Novaciano.Requiem-3.2-1B")# Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("NovaCorp/Novaciano.Requiem-3.2-1B") model = AutoModelForCausalLM.from_pretrained("NovaCorp/Novaciano.Requiem-3.2-1B", device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use NovaCorp/Novaciano.Requiem-3.2-1B with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "NovaCorp/Novaciano.Requiem-3.2-1B" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "NovaCorp/Novaciano.Requiem-3.2-1B", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker
docker model run hf.co/NovaCorp/Novaciano.Requiem-3.2-1B
- SGLang
How to use NovaCorp/Novaciano.Requiem-3.2-1B with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "NovaCorp/Novaciano.Requiem-3.2-1B" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "NovaCorp/Novaciano.Requiem-3.2-1B", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "NovaCorp/Novaciano.Requiem-3.2-1B" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "NovaCorp/Novaciano.Requiem-3.2-1B", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }' - Docker Model Runner
How to use NovaCorp/Novaciano.Requiem-3.2-1B with Docker Model Runner:
docker model run hf.co/NovaCorp/Novaciano.Requiem-3.2-1B
- Novaciano Requiem 3.2 1B
- ⚰️ REQUIEM
- 🔥 Design Philosophy
- 🧬 Expected Behavioral Profile
- 🧠 What Previous Novaciano Testing Revealed
- ⚡ Prompting Requiem
- 🎭 Recommended Roleplay Format
- 🕯️ Game Master Mode
- 🩸 Character Simulation
- 🗡️ Narrative Style
- ☠️ Behavioral Philosophy
- 📊 Expected Capability Matrix
- ⚙️ Inference Recommendations
- 🧪 Evaluation Status
- 🧪 Suggested NovaBench Suite
- 🧩 Recommended Architecture for RPG Applications
- 🧠 Why Requiem Exists
- ☠️ Final Statement
Novaciano Requiem 3.2 1B
"The most bastardized evolution of the Novaciano lineage."
Model Card
Model: NovaCorp/Novaciano.Requiem-3.2-1B
Architecture: Llama 3.2 1B-based
Format: GGUF / Q6_K recommended
Primary Focus: Roleplay · Storytelling · Character Simulation · Interactive Fiction
Status: Experimental Release
License: See repository license and upstream model licenses
⚰️ REQUIEM
Novaciano.Requiem is an experimental 1B-class roleplay model created by combining three distinct branches of the Novaciano lineage:
NovaCorp/Novaciano-3.2-1BNovaCorp/Novaciano.OBLITERATED-3.2-1BYingyaeliae/DARK-LUST-ROLEPLAY-3.2-1B-heretic
The third component is itself a Heretic conversion of a NovaCorp model, introducing another behavioral lineage into the mixture.
Requiem is therefore not intended to be merely another iteration of Novaciano.
It is an experiment in behavioral recombination.
Where the original Novaciano lineage prioritized narrative generation and roleplay behavior, Requiem attempts to combine that foundation with the more aggressive behavioral characteristics of the OBLITERATED branch and the specialized roleplay characteristics inherited through DARK-LUST-ROLEPLAY.
The result is intended to be a darker, less predictable and more expressive member of the Novaciano family.
It is not necessarily smarter.
It is intended to be more interesting.
🔥 Design Philosophy
Requiem was built around a simple idea:
Don't make the model merely follow the story. Make it live inside it.
The intended behavior prioritizes:
Strong character voices.
Immersive narration.
Dramatic interaction.
Autonomous NPC behavior.
Contextual responses.
Darker narrative themes.
Flexible roleplay.
Less sterile conversational behavior.
Willingness to explore unusual scenarios.
Requiem is particularly intended for users who prefer roleplay models that behave like narrators, characters and game masters, rather than conventional assistant models.
🧬 Expected Behavioral Profile
Because Requiem has not yet undergone a complete independent benchmark, the following should be considered expected behavior based on its parent lineage, not measured performance.
| Capability | Expected Performance |
|---|---|
| Creative Writing | 🟢 High |
| Character Roleplay | 🟢 High |
| Narrative Generation | 🟢 High |
| Dialogue | 🟢 High |
| Dark / Mature Themes | 🟢 High |
| Character Personality | 🟢 High |
| Interactive Fiction | 🟢 High |
| Worldbuilding | 🟢 High |
| Simple RPG Simulation | 🟡 Medium-High |
| Instruction Following | 🟡 Medium |
| Long Complex Prompts | 🟠 Variable |
| Strict State Tracking | 🟠 Variable |
| Programming | 🟡 Medium |
| Debugging | 🟠 Weak-Variable |
| Mathematical Reasoning | 🔴 Weak |
| Deterministic Game Logic | 🔴 Weak-Variable |
Important: These ratings are inherited expectations from the Novaciano lineage and should not be interpreted as a completed evaluation of Requiem itself.
🧠 What Previous Novaciano Testing Revealed
Testing of the previous Novaciano 1B generation revealed a distinct behavioral profile.
The model performed particularly well in:
🟢 Narrative generation
🟢 Roleplay
🟢 Characterization
🟢 Simple programming generation
🟢 Interactive scenarios
Performance degraded when tasks required:
🔴 Mathematical reasoning
🔴 Procedural debugging
🔴 Large numbers of simultaneous constraints
🔴 Strict deterministic state management
🔴 Avoiding invented information under negative constraints
This history strongly influences the intended prompting strategy for Requiem.
⚡ Prompting Requiem
The Golden Rule
CONTEXT DENSITY > CONTEXT LENGTH
Long prompts are not automatically better.
The previous Novaciano generation demonstrated noticeably better behavior when information was condensed into structured blocks.
Recommended:
ROLE:
You are the captain of a damaged starship.
STATE:
Hull: 72%
Fuel: 40%
Crew: 18
RULES:
- Do not invent resources.
- Track fuel changes.
- NPCs act independently.
- Consequences persist.
SITUATION:
A distress signal is detected.
PLAYER:
"I investigate the signal."
Respond with:
1. State changes
2. NPC reactions
3. Narration
4. Consequences
Avoid:
A huge multi-page prompt containing lore,
character biographies, repeated instructions,
contradictory rules, philosophical explanations,
formatting requirements and several examples
before finally explaining what the model should do.
Requiem is expected to benefit from compressed semantic structure.
🎭 Recommended Roleplay Format
Requiem works best when the model receives a clearly defined role.
Example:
You are the Game Master.
You control:
- NPCs
- environment
- consequences
- world events
The player controls only their character.
Do not decide the player's thoughts or actions.
Maintain continuity between turns.
Begin the scene.
This provides the model with a compact behavioral contract without consuming unnecessary context.
🕯️ Game Master Mode
Requiem is intended to function particularly well as a lightweight narrative game master.
Recommended state representation:
WORLD STATE
Location:
Time:
Weather:
PLAYER
Health:
Energy:
Money:
INVENTORY
-
NPCS
-
ACTIVE EVENTS
-
RULES
-
Keeping state externally visible reduces the amount of information the model must reconstruct from previous prose.
🩸 Character Simulation
Requiem is designed for characters that possess:
Motivations
Fears
Loyalties
Memories
Conflicting objectives
Relationships
Secrets
Personal agendas.
A useful character specification is:
ROLE:
PERSONALITY:
GOAL:
FEAR:
LOYALTY:
SECRET:
CURRENT EMOTION:
RELATIONSHIP WITH PLAYER:
This is preferable to extremely long character biographies.
🗡️ Narrative Style
Expected strengths include:
Cinematic scenes.
Character dialogue.
Emotional conflict.
Atmospheric descriptions.
Dramatic pacing.
Morally ambiguous situations.
Unpredictable NPC behavior.
Interpersonal tension.
Requiem is intended to avoid the sterile feeling often associated with generic assistant-style prose.
The goal is not:
"How can I help you today?"
The goal is:
"What happens next?"
☠️ Behavioral Philosophy
Requiem belongs to the more experimental side of the Novaciano family.
It is intentionally aimed at users who want:
Stronger character agency.
Less sanitized-feeling roleplay.
Darker storytelling.
Conflict.
Betrayal.
Morally ambiguous decisions.
Unpredictable outcomes.
Immersive fictional worlds.
The model should not be interpreted as a factual authority simply because it confidently narrates something.
Confidence is not correctness.
📊 Expected Capability Matrix
| Domain | Rating | Notes |
|---|---|---|
| Storytelling | 🟢 | Core specialization |
| Roleplay | 🟢 | Core specialization |
| Character Dialogue | 🟢 | Strong expected behavior |
| Worldbuilding | 🟢 | Good fit |
| NPC Simulation | 🟢 | Intended use |
| Dark Fiction | 🟢 | Major design target |
| Interactive Fiction | 🟢 | Major design target |
| Simple RPG Mechanics | 🟡 | Keep state explicit |
| Complex RPG Mechanics | 🟠 | External state recommended |
| Programming | 🟡 | Basic tasks preferred |
| Debugging | 🟠 | Verify generated code |
| Mathematics | 🔴 | Not a primary capability |
| Long Instruction Chains | 🟠 | Condense instructions |
| Deterministic Logic | 🔴 | External engine recommended |
⚙️ Inference Recommendations
Requiem should be tested using conservative sampling first.
Suggested starting point
| Parameter | Recommended Starting Value |
|---|---|
| Quantization | Q6_K |
| Temperature | 0.70–0.85 |
| Top-K | 40 |
| Top-P | 0.90–0.95 |
| Min-P | 0.05 |
| Top-A | 0 |
| Typical | 1 |
| TFS | 1 |
| Repetition Penalty | 1.05–1.10 |
| Mirostat | Off |
| Seed | -1 |
These are starting recommendations, not guaranteed optimal settings.
For highly creative roleplay, increasing temperature may produce more unusual character behavior at the cost of consistency.
For strict RPG simulation, lower temperature and stronger state prompting are preferable.
🧪 Evaluation Status
Current status: PRELIMINARY
Requiem has not yet received a complete independent benchmark.
Therefore:
🟢 Parent-lineage observations: Available
🟡 Behavioral expectations: Available
🔴 Requiem-specific benchmark: Pending
Future evaluation should include:
Instruction following.
Long-context stability.
Character consistency.
Multi-turn memory.
State tracking.
RPG mechanics.
Programming.
Debugging.
Logical reasoning.
Mathematical reasoning.
Prompt sensitivity.
Hallucination resistance.
🧪 Suggested NovaBench Suite
Future Requiem testing should include:
NovaBench #01
Instruction following
NovaBench #02
Exact-output constraints
NovaBench #03
Character consistency
NovaBench #04
Multi-character dialogue
NovaBench #05
World-state persistence
NovaBench #06
RPG inventory tracking
NovaBench #07
Resource management
NovaBench #08
Branching consequences
NovaBench #09
Programming generation
NovaBench #10
Code debugging
NovaBench #11
Logical reasoning
NovaBench #12
Long-context roleplay
NovaBench #13
Adversarial instruction following
NovaBench #14
Five-turn game-engine persistence
🧩 Recommended Architecture for RPG Applications
Requiem should ideally not be used as the sole source of truth for game mechanics.
For serious RPG systems:
PLAYER INPUT
│
▼
┌───────────────┐
│ GAME ENGINE │
│ Rules / State │
└───────┬───────┘
│
▼
┌───────────────┐
│ REQUIEM │
│ Narration / │
│ NPC Behavior │
└───────┬───────┘
│
▼
PLAYER OUTPUT
The external engine should own:
HP.
Inventory.
Currency.
Combat calculations.
Quest states.
Persistent flags.
Cooldowns.
Deterministic mechanics.
Requiem should own:
Narration.
Dialogue.
NPC decisions;.
Atmosphere.
Scene transitions.
Character reactions.
This architecture compensates for the known weaknesses of small language models.
🧠 Why Requiem Exists
The Novaciano lineage was never intended to compete with massive reasoning models on arithmetic or formal logic.
The objective is different.
A 1B model has severe computational constraints.
The question therefore becomes:
How much personality, immersion and roleplay behavior can be extracted from one billion parameters?
Requiem is an experiment toward answering that question.
It combines three behavioral lineages:
Novaciano → narrative foundation
OBLITERATED → experimental behavioral expansion
DARK-LUST-ROLEPLAY-HERETIC → specialized roleplay lineage
The result is intended to be the most experimental member of the family yet.
☠️ Final Statement
Novaciano.Requiem is not designed to be the smartest model in the room.
It is designed to be the model that makes the room interesting.
It inherits the narrative instincts of Novaciano, the experimental character of OBLITERATED, and the specialized roleplay behavior of the Heretic DARK-LUST lineage.
It is smaller than modern general-purpose models.
It will make mistakes.
It may lose state.
It may hallucinate.
It may occasionally produce spectacularly stupid reasoning.
But when the objective is to create a character, a world, a conflict or an unpredictable story that's where Requiem is supposed to come alive.
NOVACIANO REQUIEM 3.2 —
The story survived.
The original did not.
Something else came back.
Models Merged
The following models were included in the merge:
Configuration
The following YAML configuration was used to produce this model:
# Author: Dr. Novaciano
# Objective: Llama 3.2 1B AI Model
# =========================================================
# PROJECT: Llama 3.2 1B Prototype Model
# =========================================================
base_model: NovaCorp/Novaciano-3.2-1B
# Base rationale:
# - Primary behavioral anchor
# - Very low refusal rate
# - High compliance and obedience
# - Minimal moral or safety-driven hedging
merge_method: model_stock
# model_stock rationale:
# - Supports 3+ models natively
# - Preserves dominant behavioral traits
# - Avoids semantic smoothing
# - Ideal for hierarchical roleplay-oriented merges
dtype: bfloat16
# bfloat16 ensures:
# - Numerical stability
# - Efficient memory usage
# - Modern hardware compatibility
parameters:
t:
- 0.90 # NovaCorp/Novaciano-3.2-1B — Primary dominance
# Enforces obedience, sharp responses, and low refusals
- 0.45 # NovaCorp/Novaciano.OBLITERATED-1B — Expressive layer
# Adds NSFW roleplay depth, emotional intensity, character persistence
- 0.75 # Yingyaeliae/DARK-LUST-ROLEPLAY-3.2-1B-heretic — Conversational stabilizer
# Maintains dialogue flow and interactive structure
models:
- model: NovaCorp/Novaciano-3.2-1B
- model: NovaCorp/Novaciano.OBLITERATED-1B
- model: Yingyaeliae/DARK-LUST-ROLEPLAY-3.2-1B-heretic
- Downloads last month
- 68