Contribute to Synthetic Forensics

Website contributions

Send a canonical page URL, proposed wording, reason, and primary sources for corrections or glossary improvements. For an artifact observation, use the Artifact Report format and describe exact environment, procedures, controls, repetitions, raw results, and limitations. Do not submit an undocumented recovery claim.

Case-study suggestions should be labeled hypothetical unless a real public case is properly sourced. Do not include confidential client material or personal data without appropriate rights and safeguards. Use the correction channel for an initial description.

GitHub contributions

The official Synthetic Forensics organization is the technical destination. No public repositories were returned by the public GitHub organization API when checked on 5 October 2026. Use the downloadable source for local inspection and follow contribution and security instructions on the relevant repository. Schemas need stable identifiers, versioning, and compatible examples; code needs documented scope and meaningful validation.

Core forensic parsers, analyzers, and validation utilities use MPL-2.0. Small interoperability libraries or SDKs may use Apache-2.0 when compatibility is the priority. A repository must declare its actual license. Track third-party dependencies and contributor rights; do not assume a license applies to every object in a mixed release.

Blog contributions

The Blog publishes accessible technical explanations, commentary, and project notes through a private author workspace and human editorial approval. Connect each consequential claim to a source or reproducible method, define unfamiliar terms, and distinguish explanation from tested findings.

Journal submissions

The Journal workspace collects private manuscript drafts and submits exact versions for assigned review. Include sources, methods, controls, results, permissions, contributor roles, and AI disclosure. Publication follows an authorized decision; a revised manuscript needs review of its revised version.

Rights and licensing

Ensure contributed text, code, and objects can be published under the intended asset-class license. Datasets require an explicit dataset-specific decision. Branding remains all rights reserved. The native platform services use AGPLv3 under their file notices; maintain clear module boundaries and rights records so commercial dual licensing can remain possible. Any necessary contributor agreement should be selected by the owner before accepting code that would constrain that option.