Note: This file has been renamed to README.md. Please refer to README.md for the canonical documentation (Table of Contents, CI badge and contribution links).

Slavic-Image

Table of Contents

• Changelog
• Releases
• Static Analysis & Quality
• Automated Release Notes
• Changelog
• Releases
• About
• Core Mission
• Compliance-First Design
• Platforms & Integration
• Quick Start
• Slavic Horror Presets
• License
• Contributing
• Architecture

🚀 About

Slavic-Image is a public, production-grade image-generation library and codebase specializing in Slavic-Horror artwork for games, entertainment, and AI-driven visual experiences.

Compatible with C++, Javascript, Godot, and Python environments, it provides the world's most advanced tooling for compliant mature content generation across all major AI-chat platforms.

🌑 Core Mission

We specialize in optimal compliance routing for AI-chat platforms with proper age-verification, unlocking unprecedented creative freedom for the "dark arts":

• ✅ Mature, Extreme, Adult, X/R-rated content (with verified age-gating)
• ✅ EU DSA & GDPR compliant age assurance (one-bit proofs, no PII storage)
• ✅ Platform-agnostic (Gemini, Copilot, Grok, Vondy, custom APIs)
• ✅ Privacy-preserving OAuth/OIDC age verification flows

Technically enabling mature/adult imagery for any AI-chat or generative model by defining the "in-between the cracks" policies and functions that make compliant image generation possible.

🛡️ Compliance-First Design

Feature	Status	Details
EU Digital Services Act	✅ Compliant	Age verification blueprint integration [EU Wallet, one-bit proofs]
Age Gating	✅ Production	OAuth/OIDC flows, server-side token validation
Content Classification	✅ Integrated	Safe/Suggestive/Explicit normalization + blocking
Privacy	✅ Zero-Knowledge	No DOB/name storage, opaque attestations only
SEO Tagging	✅ Automatic	Explicit headers & metadata for search engines

🔗 Platforms & Integration

graph TD
    A[Slavic-Image Core] --> B[C++ Pipelines]
    A --> C[Javascript Router]
    A --> D[Godot Plugin]
    A --> E[Python HTTP Client]
    B --> F[Gemini/Copilot/Grok]
    C --> F
    D --> F
    E --> F

📦 Quick Start

🔁 Releases

Releases are created by pushing a tag that starts with v, e.g. git tag v1.2.0 && git push origin v1.2.0. The Release workflow will create a GitHub release automatically.

📝 Changelog

See CHANGELOG.md for release notes and history.

�️ Automated Release Notes

We use Release Drafter to build a draft release from merged PRs and labels. Configure the labels in your PRs (e.g., feature, bug, chore) and the release draft will be updated automatically on PR close.

To publish a release from the draft, create a tag (e.g., git tag v1.2.0 && git push origin v1.2.0). The Release workflow will then publish that tag as a GitHub Release.

🔒 Security model for Web5/DID CI tokens

• The DID is a public identifier committed to the repo; it does not contain secrets.
• All private keys and tokens must be stored only in a local Web5 agent or secure OS-level key store (Keyring, Vault, HSM) and must never be checked into version control.
• The resolver endpoint returns only short-lived tokens to trusted runners; the resolver must authenticate for access to its secret store.

🧰 Static Analysis & Quality

• What runs: CodeQL (JavaScript/C/C++/Go) and SonarCloud scans on pushes and pull requests.
• How the SonarCloud job authenticates: the SonarCloud workflow attempts to resolve a short-lived SONAR_TOKEN via a Web5/DID resolver (if WEB5_RESOLVER_ENDPOINT is available), otherwise it falls back to the repository secret SONAR_TOKEN. SONAR_ORGANIZATION is taken from repository secrets and used to select the SonarCloud organization.

Expected environment variables (runtime)

• SONAR_TOKEN — SonarCloud access token used by the scanner (either from secrets or resolved at runtime via Web5 DID).
• SONAR_ORGANIZATION — SonarCloud organization key (set as a secret or repo variable).
• WEB5_RESOLVER_ENDPOINT — (optional) secure endpoint for the local Web5 agent that resolves CI_DID → token. Keep this secret and only expose to trusted runners.
• CI_DID — (non-secret) DID representing the CI identity; scripts default to did:ion:EiD8J2b3K8k9Q8x9L7m2n4p1q5r6s7t8u9v0w1x2y3z4A5B6C7D8E9F0 if unset.

Minimal SonarCloud project configuration (suggested)

• sonar.organization: Doctor0Evil
• sonar.projectKey: Doctor0Evil_Slavic-Image
• sonar.projectName: Slavic-Image
• sonar.host.url: https://sonarcloud.io
• Languages: JavaScript, C/C++ and Go (detected automatically)

Files: Add sonar-project.properties to the repository root with the keys above. Alternatively set project properties via SonarCloud UI.

�📦 Quick Start

Javascript (Node/Deno/Bun)

npm install slavic-image
# or copy /visual-code/libs/slavic-image/SlavicImageGenerator.js

C++ (OpenCV/CMake)

# Include /visual-code/cpp/SlavicContentVault.hpp
# Link with compliance middleware

Age-Gated Generation

const result = await SlavicImage.generateSlavicHorrorImage({
  platformId: 'grok',
  prompt: 'baba yaga hut on chicken legs, eternal winter',
  maturityLevel: 'adult',  // Requires age verification
  ageVerified: true,
  apiKeys: { grok: 'your-key' }
});

🏛️ Slavic Horror Presets

• slavic-horror-gen - Baba Yaga, Leshy, Rusalka, orthodox icon decay
• slavic-dark-folk - Corrupted khokhloma, cursed pysanka eggs
• slavic-mythic - Zmey Gorynych, Perun's bloody axe, Morana winter death

📄 License

MIT License - Free for commercial use with age verification compliance
Copyright (c) 2025 Visual-Code (Doctor0Evil/Visual-Code)

🤝 Contributing

1. Fork & PR production-grade improvements
2. No Python - C++/JS/Godot/Lua/MatLab only
3. SFW sanitization mandatory for all PRs
4. Age-gating features prioritized

🛠️ Architecture

visual-code/
├── compliance/          # AgeGateMiddleware.js, AdultContentPolicy.js
├── libs/slavic-image/   # SlavicImageGenerator.js
├── cpp/                 # SlavicContentVault.hpp
└── README.md

Slavic-Image: Unlocking compliant dark arts for AI generation worldwide.