Know what exists. Know who can reach it. Know what happened.
Iron File Intelligence (IFI) is an evidence-driven platform for observing file systems, analyzing access, classifying information, recording activity, and preserving cryptographically verifiable forensic lineage.
Foundation status: Greenfield foundation with ISRAS 0.1.4 formally adopted prospectively from the signed acceptance boundary. The exact candidate passed local, isolated clean-clone, and GitHub-hosted validation. Earlier provisional history remains unchanged, and IFI Gate 0, Gate 1, and production readiness remain unaccepted.
- Company: Iron Signal Systems
- Product: Iron File Intelligence
- Acronym: IFI
- Repository:
Iron-Signal-Systems/iron-file-intelligence - Canonical local path:
/src/iron-file-intelligence - Development branch:
dev - Tagline: “Built on purpose. Backed by discipline. Engineered to endure.”
The former File-Access-and-DLP repository is a proof of concept and historical reference only. IFI is a clean design and implementation effort; compatibility with the proof of concept is not an architectural objective.
Source systems observe and acquire locally, then push signed and encrypted packages outward. The central evidence environment does not join Active Directory, hold domain credentials, or initiate management or file-access connections to source systems.
IFI separates filesystem observation, content acquisition, contained extraction, classification, activity and audit-health evidence, authoritative acceptance, and cryptographic lineage. It does not silently modify source files, permissions, ownership, timestamps, names, encryption state, or audit configuration.
IFI is independently deployable, testable, recoverable, supportable, and operationally useful without any external consumer. Consumer-specific adapters, mappings, storage, interpretation, and lifecycle belong to the consuming product, not to the IFI foundation.
The accepted development roadmap contains 42 small phases, numbered Phase 0 through Phase 41. Work begins with canonical evidence encoding and object identity before Windows services, transport, PostgreSQL, acquisition, extraction, classification, or activity collection are introduced.
Phase 1 Step 4 passed local, isolated clean-clone, race, ISRAS, and hosted validation at commit f6cb287b0c217f6e3be94160743fd7bc7f95a4db. Phase 1 Step 5 now retains 49 negative and malformed-input vectors and verifies exact category, stage, code, raw digest, and atomic-output behavior through the Go processor and a separate Python standard-library reference path. Step 5 changes no production canonicalizer source and does not accept Gate 1.
make validate
make positive-vectors
make negative-vectorsThe committed .isras/project.json additionally defines the exact ISRAS Go-profile commands executed locally and by the immutable hosted workflow.
Start with the documentation index, project charter, target architecture, implementation roadmap, and acceptance gates.
Except for identified branding and third-party exclusions, Iron File Intelligence is distributed under the Business Source License 1.1 (BUSL-1.1):
- Licensor: John Wood
- Additional Use Grant: None
- Change Date: 2030-07-18
- Change License: GNU Affero General Public License, Version 3
BSL 1.1 is source-available but is not an Open Source license before the Change Date. See LICENSE, LICENSING.md, and the licensing status.