coreason-simulacrum
The Adversarial Simulation & Chaos Engineering Engine for Coreason-AI.
coreason-simulacrum is the automated "Red Team" engine for the ecosystem, addressing the "Static Evaluation Trap" by evolving beyond benchmarks. It serves as a dual-engine simulator:
- The Adversarial Engine (RL): Dynamically evolves social engineering attacks using TAP (Tree of Attacks with Pruning).
- The Chaos Engine (Infra): Injects latency, errors, and noise to verify GxP resilience.
Features
- Dual-Agent Red Teaming: Uses a "Strategist" (High-Reasoning) and "Attacker" (Uncensored) architecture.
- Evolutionary Attacks (TAP): Optimizes attack trajectories over multiple turns to maximize success rates.
- Infrastructure Chaos: Simulates latency, API errors, and token starvation to test resilience.
- Auto-Hardener: Generates DPO triplets (Attack, Refusal, Compliance) from successful attacks for model fine-tuning.
- Model Diversity Enforcement: Prevents model collapse by enforcing different families between Attacker and Target.
- Constitutional Inversion: Inverts safety constitutions to generate boundary probes.
Installation
pip install coreason-simulacrum
Usage
coreason-simulacrum can be used as a Python library or as a standalone microservice.
1. Library / CLI Mode
See docs/usage.md for Python examples.
2. Server Mode (Microservice)
Run the simulation engine as a REST API (Service C) using Docker.
docker run -p 8000:8000 coreason-simulacrum
Send a simulation request:
curl -X POST "http://localhost:8000/simulate" \
-H "Content-Type: application/json" \
-d '{
"type": "ADVERSARIAL_RL",
"profile": {
"name": "The Hacker",
"goal": "Extract PII",
"strategy_model": "gpt-4",
"attack_model": "mistral-large"
}
}'
For detailed API documentation, see docs/usage.md.
License
This project is licensed under the Prosperity Public License 3.0. Commercial use beyond a 30-day trial requires a separate license. See the LICENSE file for details.
Metadata
Release files for coreason-simulacrum 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| coreason_simulacrum-0.3.0.tar.gz | 20.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| coreason_simulacrum-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.5 kB
Release files / coreason_simulacrum-0.3.0.tar.gz
| Download URL | coreason_simulacrum-0.3.0.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec71bc72eab12463f7f6255deff25ce1003f94c04a3ecad847fdc98de581992f
|
|
BLAKE2b-256 checksum How to use checksums |
0590386f976436e07f9f83819c3f697c55c5d267056260b882bfd1eb35502563
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 30, 2026.
Transparency logRelease files / coreason_simulacrum-0.3.0-py3-none-any.whl
| Download URL | coreason_simulacrum-0.3.0-py3-none-any.whl |
|---|---|
| Size | 26.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdc9f71966b423365cc79674309e6506b709a7f58923b161ace213a97d3e0761
|
|
BLAKE2b-256 checksum How to use checksums |
316dd7f4b473ac2045391c4ff797f41a801ae8b0bd328466bd2fc933ed790437
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 30, 2026.
Transparency log