Skip to content

⚡ SYSTEM: ANOMALY // TEMPLATE_VAULT (MKDOCS)

STATUS: ONLINE // ENGINE: MKDOCS MATERIAL + OBSIDIAN BRIDGE // CLASSIFICATION: PROFESSIONAL / STRUCTURED

"We do not just build software. We construct the impossible." — Anomaly Blueprint

🎯 MISSION PROFILE: THE "STRUCTURED" PROTOCOL

This vault is built on the MkDocs engine. It is engineered for high-stakes deliverables that demand structure, clarity, and a trustworthy, professional presentation.

Primary Use Cases:

  • 📘 Standard Operating Procedures (SOPs)
  • 📄 Technical Contracts & Scope of Work
  • 🔧 API Documentation & SDK Manuals
  • 🧭 User Guides & Handbooks
  • 🏛️ HR & Legal Policy Documents

While optimized for linear, structured content, this engine is fully capable of handling rich media and complex data for any project that requires a polished, corporate aesthetic.

📡 OPERATIVE ONBOARDING

Welcome to the Anomaly Blueprint secure documentation grid. This vault serves as the Master Mold for your project's data.

🔄 THE "INVISIBLE GIT" WORKFLOW

You are viewing the Live Rendered version of this document. Your workflow is designed to be seamless:

  1. Write in Obsidian: Open this folder in your Obsidian editor. Edit files, drag images, and link pages naturally.
  2. Auto-Sync: The system automatically pushes your changes to the secure cloud via Git.
  3. Live Deployment: Within minutes, this website updates to reflect your work.

🛠 FIELD MANUAL: CYBERNETIC TOOLS

This engine is equipped with Category-5 Enhancements. Use the following protocols to maintain visual supremacy directly from Obsidian.

1. INTELLIGENCE BLOCKS (Callouts)

Use standard Obsidian "Callout" syntax. The system automatically converts them into high-fidelity UI elements.

MISSION INTEL

This is an standard > [!INFO] block. Use it for general context.

TACTICAL ADVANTAGE

This is a > [!TIP] block. Use it for best practices or shortcuts.

HAZARD DETECTED

This is a > [!WARNING] block. Use it for critical risks or deprecated logic.

CRITICAL FAILURE

This is a > [!DANGER] block. Use it for fatal errors or forbidden actions.

You do not need to worry about file paths. Just use double brackets to link any node in the database.

  • Standard Link: [[Phase 01 - Genesis]] -> Renders as a clickable link.
  • Aliased Link: [[Phase 01 - Genesis|Click here to start]] -> Renders with custom text.

3. MISSION TRACKERS (Task Lists)

Track operational progress using interactive checklists.

  • Phase 01: Initialize Repository (Completed)
  • Phase 02: Draft Game Design Document (Pending)
  • Phase 03: Client Approval (Locked)

4. DATA ORGANIZATION (Tabs)

Use tabs to organize dense technical specifications without cluttering the interface.

Role: Tank / Crowd Control

  • HP: 1500
  • Armor: Heavy Plate
  • Passive: Iron Will (Regenerate 1% HP per second)

Role: DPS / Stealth

  • HP: 800
  • Armor: Nano-Weave
  • Passive: Ghost Step (Invisible when sprinting)

Role: Support / Hacking

  • HP: 600
  • Armor: Light Vest
  • Passive: Overclock (Hack speed +50%)

5. SCHEMATIC INJECTION (Code Blocks)

Embed technical schematics with full syntax highlighting.

PlayerController.cs
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
// Unity C# Control Script
using UnityEngine;

public class AnomalyController : MonoBehaviour {
    public float speed = 10.0f;

    void Update() {
        // Execute Movement Protocol
        float moveX = Input.GetAxis("Horizontal") * speed;
        transform.Translate(moveX, 0, 0);
    }
}

6. VISUAL ASSETS

Drag and drop images directly into Obsidian. The system handles the pathing automatically. logo.png Tip: Place images in the assets folder for best organization.

🚀 INITIALIZATION PROTOCOL

You are currently viewing the Root of the documentation. Your first step is to establish the folder hierarchy based on the project type.

How to create sections: 1. Create a numbered folder in Obsidian (e.g., 01_Scope). 2. Inside it, create a file named index.md. 3. The system will automatically add it to the navigation bar.

📂 ARCHITECTURE BLUEPRINTS

Choose a structure below and replicate the folders in your vault.

Best for: SOWs, Retainers, Non-Disclosure Agreements.

  • 📂 01_Executive_Summary (Project Goals, Timeline Overview)
  • 📂 02_Scope_of_Work (Deliverables, Milestones, Exclusions)
  • 📂 03_Commercials (Payment Schedule, Licensing, IP Rights)
  • 📂 04_Terms_and_Conditions (Termination, Liability, SLA)
  • 📂 99_Appendices (Reference Materials)

📘 OPTION B: THE "TECHNICAL MANUAL"

Best for: API Docs, SDK Guides, Employee Handbooks.

  • 📂 01_Getting_Started (Installation, Quick Start)
  • 📂 02_Core_Concepts (Architecture, Data Flow)
  • 📂 03_API_Reference (Endpoints, Auth, Errors)
  • 📂 04_Tutorials (Step-by-Step Guides)
  • 📂 05_FAQ (Troubleshooting)

🎮 OPTION C: THE "GDD" (Structured)

Best for: Game Design Documents that need to be linear and printable.

  • 📂 01_High_Level_Concept (The Hook, USP, Pillars)
  • 📂 02_Gameplay_Mechanics (Controls, Loops, Combat)
  • 📂 03_Story_and_World (Characters, Lore, Scripts)
  • 📂 04_Assets_and_Audio (Style Guide, Sound FX)
  • 📂 05_Technical_Requirements (Engine, Platforms)

END OF FILE // TERMINATING SESSION