Software Creation: Black Core – Industrial Cyber-System for 3d Manufacturing & Api Orchestration

Black Core is a production-grade industrial automation platform designed to operate a professional 3D printing farm focused on high-value technical manufacturing.

This is not an MVP or prototype. It is a real 24/7 commercial production system intended to generate measurable profit and scale reliably without ongoing developer dependency after delivery.

Initial deployment: 6 QIDI MAX4 printers in Naples (Italy).
Mandatory scalability: 30+ machines including Lanzarote (Spain) expansion.

The system must be modular, deterministic, fault-tolerant, and suitable for long-term industrial operation.

---

## Core Functional Scope

The platform must:

• Integrate real APIs (Xometry mandatory + one of Treatstock/Hubs/Craftcloud).
• Track full order lifecycle (seen, quoted, won, rejected).
• Guarantee strict idempotency (no duplicate jobs, no duplicate API calls, no duplicate prints).
• Evaluate profitability before job acceptance.
• Assign production based on real machine state.
• Monitor production via firmware/API telemetry.
• Automate ZPL labeling (Zebra ZT411) only after verified job completion.

Human micromanagement must be minimized. Determinism and operational continuity are mandatory.

---

## Deterministic Architecture

The system must ensure:

• No lost state after restart
• No corrupted queues
• No undefined states
• No duplicated operations under retry or reboot

All critical operations must be:

• Persisted before execution
• Restart-safe
• Idempotent
• Fully traceable via structured logs

After power failure or forced reboot, the system must resume without losing order state or duplicating jobs.

Local state is the single source of truth.

---

## Hardware-State Validation (QIDI MAX4)

Production must be validated against real firmware/API telemetry.

Mandatory checks:

• Bed and chamber thermal stability before job start
• Detection of exposed hardware anomalies
• Immediate safe halt in case of instability

Software-only assumptions are not acceptable.

---

## Energy & Electrical Control

Sequential warm-up logic is required to prevent electrical spikes exceeding facility capacity.

Requirements:

• Configurable machine concurrency
• Configurable power thresholds
• Prevention of simultaneous heating peaks

Production must not cause electrical overload conditions.

---

## Profitability Engine

Each job must be evaluated using a deterministic cost model including:

• Real material usage
• Energy consumption (machine time × local kWh cost)
• Machine depreciation per operational hour
• Configurable minimum margin-per-hour threshold

Orders below threshold must be automatically rejected.

---

## Resilience & Monitoring

• Independent queues per machine
• Automatic reassignment if a machine fails
• Offline-first operation (local production continues if internet fails)
• Central dashboard with up to 6 video feeds

Real-time alerts via Telegram and/or WhatsApp for filament run-out, thermal anomalies, hardware errors, and system faults.

---

## Backup & Disaster Recovery

The system must include a native full backup and restore mechanism:

• Full environment export (database, configurations, logs, production state)
• Restore to new hardware without developer intervention
• Deterministic recovery behavior

The system must remain fully operable after hardware replacement.

---

## Infrastructure & Security

• Bare-metal Linux server
• Hardened os configuration
• vpn-only access (wireguard or equivalent)
• strong authentication with 2fa
• vlan separation between video and machine-control traffic

---

## delivery & validation

timeline: 60–90 calendar days
budget: $2,000 usd fixed
single escrow milestone

payment released only after validation on real hardware including:

• restart safety test
• blackout recovery test
• multi-day uninterrupted production test

---

## ownership & independence

• 100% source code ownership transferred to client
• code delivered to client-owned private repository
• all developer access credentials revoked at delivery
• no remote dependency, no recurring access required

bug fixes for defects directly related to delivered scope must not require permanent system access and must not create financial dependency.

The system must operate independently of the original developer.

---

## Scope Integrity Clause

Everything technically necessary to deliver a stable, production-ready system is included in this scope and budget, even if not itemized line-by-line.

No additional phases, hidden dependencies, recurring fees, maintenance retainers, or post-delivery financial obligations will be accepted.

---

## Mandatory Proposal Filter

Proposals must begin with:

“napoli–lanzarote | black core | 60-90 days | ready”

Proposals missing this phrase will not be reviewed.