Home/Products

Products and boundaries

The tool produces data and evidence; the compliance verdict stays with people and the customer's system. That boundary is what keeps it at DO-330 TQL-5.

SCOPE

What it does, what it refuses to do

IN SCOPE

  • Acquisition and reproduction from a config deposit, restored to an exact SHA
  • Configuration items and the configuration index
  • Baselines: component freeze, system BOM, derivation and status
  • Access policy provisioning and drift verification
  • Status accounting, environment configuration, build records, bidirectional traceability
  • Retrieval, release, evidence export and offline verification

OUT OF SCOPE

  • Full change-request lifecycle — a sibling change-management project
  • Diff rendering and GUI — git-diff-html and a separate GUI project
  • Compiling, running tests, exporting images — the customer's CI
  • Automatic verification or compliance verdicts
  • Reverse engineering commercial CM tools

One principle: if a control can be enforced by platform permissions, it belongs to the platform. The tool handles only the semantics and evidence the platform cannot.

01CFDEPOSIT · VERSION CONFIGURATION

cfdeposit: turning §7 objectives into exportable evidence

Gerrit is an excellent content-version and hash foundation, but it has no notion of configuration items, baselines or status accounting. cfdeposit adds exactly that layer.

Command set (v1 draft, aligned with the tool operational requirements)
CommandPurposeKey options / output
depositFreeze a component, emit its config deposit--sha --label --cr --comment
deposit --specBuild the system baseline BOM--spec --system
syncFetch and restore exactly to a SHA--into --offline --jobs
audit-exportExport an offline-verifiable bundle--out → evidence-bundle.v1
verify-bundleVerify a bundle without the toolCHECKSUMS + bundle-deposit
precheckSandbox pre-check, no markers written--json
show / list / withdrawQuery, list, withdraw a baseline--label --system

FAIL-FAST INPUT RULES

No loose version references

Non-SHA, branch names and short SHAs are rejected; never falls back to the branch tip.

Unregistered items rejected by default

Anything outside the manifest needs explicit allowance, and the allowance is recorded.

Gate failure fails the whole run

Missing CI, open change requests or illegal inheritance abort the command with a full failure list.

OUTPUT

config depositJSON, every entry pinned to a SHA
bom.jsonSystem composition, components[] to labels
ledger.jsonlEvent ledger, prev_hash chained
evidence-bundleDirectory + CHECKSUMS + standalone verifier

Binaries never enter the source repository: the artifact repository holds the bytes, the deposit holds hash and location.

02GIT-DIFF-HTML · REVIEWABLE DIFF

Making the review itself archivable

Review records often boil down to one line: “approved”. This tool renders diffs into structured static pages, grouped by commit and file, ready for the evidence bundle.

Output is self-contained HTML with no server or external assets, designed for long-term archiving. git-diff-html 1.2.1-1 is available in Debian forky / sid through the official package channel.

USAGE

git-diff-html --repo . --from main --to HEAD --out diff-report.html

FEATURES

  • Grouped by commit, file and hunk
  • Static output, no server dependency
  • Attachable to a baseline evidence bundle
  • Debian package and source channels
03TASKHEALTH · RUNTIME HEALTH

Filling the gap in Linux thread-level health monitoring

systemd watches processes, not threads. TaskHealth pairs a daemon with a client library to bring thread-level anomalies into one view.

taskhealthdDAEMON

Background collection

A resident service collects heartbeats and state from clients, records anomalies and applies the configured policy.

libtaskhealthCLIENT LIB

Light integration

Business threads join monitoring with a few calls, no extra dependencies, C11, Linux 3.x and later.

packagingDISTRO

Engineered delivery

Man pages and systemd units included, packaged as .deb, RPM and Yocto.

Licence split: client library MIT, daemon GPL-2.0. Commercial and open-source boundaries are explicit; the same code is not billed twice.

04SYMTHOSM653 · ARINC 653 PARTITIONED OS

A partitioned kernel is not a preference, it is the only closable path

Linux cannot directly close the timing argument for DAL A/B. A partitioned kernel fixes execution windows in a major frame and turns worst-case behaviour into something provable.

Key characteristics
StandardARINC 653 Part 4 functional requirements
IsolationMajor-frame scheduling (temporal) + memory partition protection (spatial)
Health monitoringModule / partition / process fault isolation and recovery
Portabilityaarch64, one-command QEMU verification
EngineeringDeclarative .config.mk, APEX static library and SDK

Benchmark and route

Benchmarked against VxWorks 653 and INTEGRITY-178B on determinism and function coverage, on a domestic-replacement route. The first release targets a verifiable partitioned kernel and health monitoring, adding certification evidence step by step.

USER SDK · ENCRYPTED KERNEL + APEX LIBRARY

The public repository contains the user SDK (encrypted kernel, APEX static library, headers and configuration tools). Partition-kernel source is not public; request an evaluation through the trial form.

git clone https://github.com/LuHaoran1981/Symthosm653.git
05LICENSING

Open source, trial, commercial

Indicative boundaries; the signed licence agreement takes precedence
CapabilityOpen sourceTrialCommercial
Diff rendering, runtime monitoringfullfullfull
Configuration items and indexnolimitedfull
Component freeze and system baselinesno3 baselinesunlimited
Evidence export and offline verifynowatermarkedfull
Server-side checks and central auditnonooptional module
Support and qualification kitcommunityemailcontractual