FootCode is a self‑contained, tamper‑resistant, hardware‑aware programming ecosystem designed for secure distribution, reproducible builds, and zero‑install execution. It introduces sealed dependency containers, hardware‑tailored machine‑code output, triple‑profile compilation, redundant metadata, encrypted structural fingerprints, and strict signature validation.
Dependencies are distributed as either:
- Source (
.fc) - FootCode Language System Container File (
.fclscf)
.fclscf files contain:
- Preprocessed source
- Dependency metadata
- Execution‑bias group
- Architecture profile
- Encrypted class‑initial fingerprint
- Signature and integrity data
No global installs. No toolchains. No version conflicts.
Every project and dependency is compiled into three .bin variants:
- A: CPU‑Bound
- B: Balanced
- C: GPU‑Bound
Each variant contains hardware‑tailored machine code optimized for its execution bias. The dependency reader automatically selects the correct variant at runtime.
[FootCode]config- Version
- Architecture
- Execution‑bias group
- Safety flags
- Dependency metadata
- Hardware‑specific machine code
- Optimized for CPU/Balanced/GPU
- UTF‑8 metadata copy
- Encrypted class‑initial fingerprint
- Signature
- EOF marker
- Offset + length table
Any modification invalidates the file.
FootCode embeds an encrypted fingerprint derived from:
- The first character of every class
- Deterministic concatenation
- AES‑256 or ≥1 KiB padded encryption
- Included in signature input
This prevents class tampering, dependency spoofing, metadata forgery, and reverse‑engineering of project structure.
The dependency reader is the only installed component. It handles:
- Dependency resolution
- Signature validation
- Metadata verification
- Fingerprint decryption
- Execution‑bias selection
- Architecture matching
.binloading
Everything else is fetched from local disk, LAN server, or the internet.
FootCode is designed for secure environments, reproducible builds, sealed execution, anti‑tamper distribution, hardware‑aware optimization, and dependency isolation. It eliminates global toolchains, version conflicts, and accidental or malicious binary modification.
Although FootCode is intended to be MIT‑licensed, contributors must follow the project's development and deployment rules to maintain ecosystem integrity.
- All dependencies must be provided as
.fcsource or.fclscfcontainers. - Every build must output CPU‑Bound, Balanced, and GPU‑Bound
.binvariants. - All
.binfiles must include valid metadata, encrypted fingerprints, and signatures. - No tampering, patching, or manual modification of generated
.binfiles. - All contributions must preserve the sealed‑execution model.
- Deployment pipelines must validate signatures and metadata before publishing artifacts.
These rules ensure FootCode remains deterministic, secure, and tamper‑resistant across all environments.
FootCode is the compiler and fcpcts is the Terminal Package and Config service (Client only needs fcpcts installed).
The fcpcts is a simple extension of Powershell which gives FootCode compatibility with Windows and also fcpcts handles config reading and package management, it also handles emergencies where the device physically can't handle the code.