DarkMatter VoidCrawler icon DarkMatter Software // Developer Systems
Release 0.2.0 // Build Forge Online

DarkMatter Software // VoidCrawler Engineering Environment

VoidCrawler
Developer Edition

Configure, validate, compile, and export custom Go and PHP editions of the VoidCrawler directory intelligence system.

Release 0.2.0 Targets Go + PHP Desktop PySide6 Build Compiled + Validated

Developer Edition Overview

Immutable Templates // Repeatable Builds

VoidCrawler Developer Edition is the engineering layer for the VoidCrawler ecosystem. It does not replace the working Go or PHP runtimes. It preserves them as controlled source templates, applies project-specific configuration, validates the resulting deployment, compiles the Go server into a real executable, and exports clean target directories ready for testing or production staging.

Builder Release0.2.0
Go RuntimeCompiled vcu
PHP RuntimeDeployable Source
Project Format.vcproject.json

Controlled Source Generation

Working template files remain untouched. Each build is generated into a new output directory, preventing configuration work from corrupting the known-good source environment.

Dual-Target Engineering

Build the standalone Go server, the PHP web-service edition, or a synchronized Unified project that produces both targets from one shared configuration.

Executable Build Contract

A Go export is not considered complete until the generated vcu.go compiles successfully into the configured executable and the binary is validated.

System Architecture

Templates // Projects // Exports

The Developer Edition separates immutable runtime DNA from editable project blueprints. This is the central design rule of the application and the reason custom builds remain reproducible.

Template Layer

  • Known-good Go source
  • Known-good PHP source
  • Canonical PHP stylesheet
  • Unmodified runtime behavior

Project Layer

  • Target selection
  • Identity and version metadata
  • Hidden directories and filenames
  • Hidden extensions
  • Go and PHP target settings

Export Layer

  • Generated source
  • Compiled Go executable
  • PHP deployment package
  • Copied interface assets
  • Build manifests and checksums
DarkMatter_VoidCrawler_Developer_0.2.0/
├── app.py
├── cli.py
├── assets/
│   └── images/
│       ├── billboard.png
│       └── icon.png
├── templates/
│   ├── go/
│   │   └── vcu.go
│   └── php/
│       ├── voidcrawler.php
│       └── voidcrawler.css
├── projects/
├── exports/
└── voidcrawler_dev/
    ├── core.py
    └── gui.py

Developer Workspace

GUI 0.2.0

Release 0.2.0 replaces the original compressed tab form with a focused developer workspace. The interface is organized around the lifecycle of a VoidCrawler build rather than around arbitrary form groupings.

Project Explorer

Navigate dedicated workspaces for Project & Identity, Visibility Rules, Asset Manager, Target Settings, Validation, and Build & Export.

Asset Manager

Inspect the canonical assets/images/ source, preview supported images, verify export filenames, and confirm the files copied into each target.

Validation Console

Check required templates, assets, compiler availability, PHP lint support, configured filenames, duplicate rules, and output readiness before building.

Asynchronous Build

Go compilation and export work run through a build worker so the desktop interface remains responsive while the toolchain is active.

Persistent Workspace

Window geometry, selected workspace, export destination, and recent operating context are retained between sessions.

Human-Readable Codebase

The GUI is divided into focused classes and methods with explicit Qt imports, structured signal connections, and maintainable synchronization logic.

Build Targets

Go // PHP // Unified
Capability Go Standalone PHP Web Service Unified Build
Primary Output Compiled vcu executable plus generated source Deployable PHP and CSS files Both target packages from one project
Interface Assets go/assets/images/ php/assets/images/ Copied into both targets
Visibility Rules Generated Go maps Generated PHP arrays Shared rules translated per runtime
Validation Go compiler, binary, checksum, executable state Template checks and PHP CLI lint when available Full validation for both target families
Best Use Portable local or standalone HTTP service Shared hosting and existing web-server deployments Mirrored development and production packages

Visibility Engineering

Default Rules + Project Overrides

VoidCrawler is designed to scan the selected root while withholding application internals, server artifacts, sensitive file types, and interface assets from the rendered repository view. The Developer Edition centralizes those controls instead of forcing developers to edit Go maps or PHP arrays by hand.

Hidden Directories

Suppress entire directory branches from the rendered crawler hierarchy. The canonical assets directory is hidden by default while its image files remain available to the interface route.

Hidden Filenames

Remove exact filename matches such as index files, branding assets, metadata images, server configuration files, and other project-specific entries.

Hidden Extensions

Exclude classes of files such as PHP, CSS, database, SQL, executable-support, or configuration formats without enumerating each filename.

Developer note: Visibility rules control what VoidCrawler renders and exposes through its generated file links. Treat every custom build as an explicit publication boundary and validate the final output against the actual repository structure before deployment.

Canonical Asset Pipeline

Single Source // Dual Export

The application maintains one canonical image source under assets/images/. During export, the builder creates the correct target structure and copies those files into the generated Go and PHP packages. Template-local duplicate asset directories are not required.

# Canonical source inside the Developer Edition
assets/images/
├── billboard.png
└── icon.png

# Generated Go target
go/assets/images/
├── billboard.png
└── icon.png

# Generated PHP target
php/assets/images/
├── billboard.png
└── icon.png

billboard.png

Primary interface hero image and Open Graph image for the Developer Edition release page.

icon.png

Application identity image used for interface branding, browser metadata, and release presentation.

Export Contract

The builder creates assets/images/ automatically in each selected target and copies canonical assets before declaring the build complete.

Developer Quick Start

Install // Configure // Build

The kit includes the desktop interface, command-line builder, runtime templates, project model, asset pipeline, installer, and packaging support. Python 3 and the Go toolchain are required for Go or Unified exports.

# Extract the full kit
unzip DarkMatter_VoidCrawler_Developer_0.2.0.zip
cd DarkMatter_VoidCrawler_Developer_0.2.0

# Create the Python environment and install dependencies
chmod +x installer.sh build.sh
./installer.sh

# Launch the desktop builder
./.venv/bin/python app.py

01 // Create Project

Choose Go, PHP, or Unified; define project identity, version, environment, and target filenames.

02 // Configure Rules

Review hidden directories, filenames, extensions, canonical images, and target-specific settings.

03 // Validate

Run the validation workspace and resolve missing templates, assets, compiler tools, or invalid output settings.

04 // Build

Export generated source, compile the Go executable, lint PHP when available, and produce manifests.

05 // Test

Run the generated target from its export directory and verify repository visibility, assets, links, and deployment behavior.

06 // Promote

Move the tested output into staging or production without modifying the Developer Edition templates.

Command-Line Builder

Repeatable Automation

The desktop interface and CLI use the same project model and core build engine. Saved project files can therefore be rebuilt without reopening the GUI, making the Developer Edition suitable for scripted release workflows and repeatable environment generation.

# Build a saved project
./.venv/bin/python cli.py \
    projects/example.vcproject.json \
    --output ./exports

# Go and Unified projects automatically compile vcu.
# Compilation is mandatory and no separate --compile-go flag is required.

Generated Output

Source + Runtime + Manifest
VoidCrawler-Exports/
└── New_VoidCrawler_Build/
    ├── go/
    │   ├── vcu
    │   ├── source/
    │   │   └── vcu.go
    │   ├── scripts/
    │   │   ├── launch.sh
    │   │   └── launch_headless.sh
    │   ├── assets/
    │   │   └── images/
    │   │       ├── billboard.png
    │   │       └── icon.png
    │   └── BUILD_INFO.json
    └── php/
        ├── voidcrawler.php
        ├── voidcrawler.css
        ├── assets/
        │   └── images/
        │       ├── billboard.png
        │       └── icon.png
        └── BUILD_INFO.json

Go Manifest

Records compiler version, command, binary name, size, executable state, SHA-256 checksum, project configuration, and generation timestamp.

PHP Manifest

Records project configuration, generation timestamp, target identity, and PHP lint results when the local CLI is available.

Portable Build Directory

Each target contains its own runtime files and copied assets, allowing the package to move independently of the Developer Edition installation.

Development Requirements

Toolchain Readiness
ComponentPurposeRequirement
Python 3Runs the GUI, CLI, project model, validators, and export pipeline.Modern Python 3 with virtual-environment support.
PySide6Provides the desktop Project Explorer, editors, validation workspace, asset preview, and build console.Installed by installer.sh.
Go ToolchainCompiles generated vcu.go into the required standalone executable.Required for Go and Unified targets; go must be available in PATH.
PHP CLIRuns syntax lint against generated PHP deployments.Recommended. Builds continue with a clear notice when unavailable.
PyInstallerPackages the Developer Edition desktop application for distribution.Used by the included build script.

Security Model

Controlled Exposure Required

Review Generated Rules

Inspect every hidden-directory, hidden-file, and hidden-extension entry before publishing a build against real content.

Protect Network Access

Use authentication, network allowlists, VPN access, reverse-proxy controls, or an equivalent boundary when the repository is not intended for unrestricted public access.

Test Exact Paths

Verify both rendered navigation and direct file routes. A hidden listing entry is not automatically equivalent to a complete authorization system.

Operational warning: VoidCrawler is a controlled directory intelligence and retrieval system, not a substitute for operating-system permissions, web-server authorization, or application authentication. The developer remains responsible for the repository root and every file intentionally exposed by the generated runtime.

Developer Edition History

Current Build Record
0.2.0

Major GUI upgrade. Added Project Explorer navigation, dedicated workspaces, Asset Manager, validation page, asynchronous build worker, persistent interface settings, improved build summary, and a fully reorganized human-readable GUI implementation.

0.1.1

Added the canonical asset export pipeline. The builder now creates assets/images/ in Go and PHP outputs and copies master images into each generated package.

0.1.0

Made Go compilation mandatory. Generated source is compiled into the configured executable, validated, checksummed, and recorded in the build manifest.

0.0.1

Initial Developer Edition scaffold with project files, Go/PHP/Unified target selection, visibility-rule editors, source generation, export directories, CLI support, and PyInstaller packaging structure.

Full Developer Kit

Release Package

DarkMatter VoidCrawler Developer 0.2.0

Complete desktop builder, CLI, templates, canonical assets, project model, validation system, compulsory Go compilation pipeline, PHP export support, installer, and packaging files.

Download Developer Kit

License & Attribution

DarkMatter Software

VoidCrawler and VoidCrawler Developer Edition are developed by K0NxT3D under the DarkMatter Software project identity. Preserve applicable copyright, license, and attribution notices when modifying or redistributing substantial portions of the software.