Tracepoint

R.00 DoD financial statement audit remediation

The evidence behind a closed finding, assembled while the work happens.

It runs on one machine and makes no network calls, hashes every file with SHA-256, and hands a reviewer a TraceSeal package that opens with nothing installed.

The worked example's activity trail, drawn as one line 19 rows appended in order by 2 people across 4 kinds of action, rising from the first kind of work to the last and ending at the workspace seal. Balance support Corrective action Evidence Attestation 1. Checking Account Balance (Dana Reyes, 2026-09-29) 2. source-control-total (Dana Reyes, 2026-09-29) 3. subsidiary-ledger (Dana Reyes, 2026-09-29) 4. general-ledger (Dana Reyes, 2026-09-29) 5. adjusted-trial-balance (Dana Reyes, 2026-09-29) 6. A $7,000 deposit was entered into the records twice (Dana Reyes, 2026-09-29) 7. $3,000 of cash spending with no receipts (Dana Reyes, 2026-09-29) 8. No one was assigned to do the monthly bank check, and there was no che (Dana Reyes, 2026-09-29) 9. No one was assigned to do the monthly bank check, and there was no che (Dana Reyes, 2026-09-29) 10. Put the monthly bank check on the supervisor’s calendar (Dana Reyes, 2026-09-29) 11. Supporting document, monthly bank check (Dana Reyes, 2026-09-29) 12. Supporting document, monthly bank check (Dana Reyes, 2026-09-29) 13. No one was assigned to do the monthly bank check, and there was no che (Dana Reyes, 2026-09-29) 14. No one was assigned to do the monthly bank check, and there was no che (Dana Reyes, 2026-09-29) 15. No one was assigned to do the monthly bank check, and there was no che (Dana Reyes, 2026-09-29) 16. Proof the fix worked, month 1 (Dana Reyes, 2026-09-29) 17. Sustainment cycle 1 (Dana Reyes, 2026-09-29) 18. Proof the fix worked, month 2 (Sam Carter, 2026-09-29) 19. Sustainment cycle 2 (Sam Carter, 2026-09-29) TraceSeal root digest 3a493632, over every row above Seal
Fig 00 The worked example's activity trail, one node per row, ending at the seal Drawn from the product's own data
The Tracepoint Case Desk: open corrective actions, their evidence, and the activity trail, on a dark interface
Fig 01 A screen recording of the application, working the example from the Case Desk to the exports page: a control link confirmed, a sustainment cycle recorded, evidence attached with its SHA-256 Shown at 1.873 times real speed Synthetic data
Awardable. Chief Digital and Artificial Intelligence Office, Tradewinds Solutions Marketplace.

Tracepoint is Awardable on the CDAO Tradewinds Solutions Marketplace.

Notice dated 23 October 2026. The listing can be viewed only with a government login. Read the record

8thconsecutive disclaimer of opinion on the FY2025 DoD financial statements
31 Dec 2028statutory deadline for a clean opinion on the DoD financial statements
1,911 of 2,485FY2025 findings were reissued from a prior year, and 929 carried no remediation date, per the DoD OIG
33of about 3,700 validated corrective action records had one required field substantively populated, per GAO

Sources: DODIG-2026-081, GAO-26-109115 (May 2026), GAO-24-106890 (September 2024), and DODIG-2026-032

The audit calendar Eight fiscal years of full-scope audit from FY2018 to FY2025, each ending in a disclaimer of opinion, and the statutory deadline for a clean opinion on 31 December 2028. FY18 FY19 FY20 FY21 FY22 FY23 FY24 FY25 FY26 FY27 FY28 FY2018: disclaimer of opinion FY2019: disclaimer of opinion FY2020: disclaimer of opinion FY2021: disclaimer of opinion FY2022: disclaimer of opinion FY2023: disclaimer of opinion FY2024: disclaimer of opinion FY2025: disclaimer of opinion First full-scope audit 8th disclaimer Clean opinion due 31 Dec 2028

The audit calendar: eight full-scope audits since FY2018, eight disclaimers, 622 findings reissued seven times over, and the statutory deadline for a clean opinion. Fiscal years, per GAO-26-109115 and DODIG-2026-081.

R.01 The Tradewinds submission

Tracepoint: From Audit Findings to a Verifiable Remediation Package.

The five-minute submission film, with captions, the abstract and keywords as submitted, the four scored criteria mapped to the film and to the evidence on this site, and the six supporting documents, all on one page.

The film's title card

R.02 See it work

This is the real application, one step at a time.

Each frame in the walk-through is a capture of the shipping application working the synthetic worked example, from the first screen to a sealed package. The film at the top of this page shows the same flow in motion.

Tracepoint as it first opens, asking what you received, before any data is loaded
First screen, what did you receive Synthetic data

R.03 How the work is recorded

Five things that currently happen by hand.

Each step leaves a record of who did it, what they saw, and what the file looked like when they saw it.

01Import

Bring a findings register in with its lineage intact

CSV, Excel, or a Word table. More than fifty fields are recognised and kept distinct: an auditor's recommendation and management's response are different statements and never merge. The file's SHA-256 is recorded, every source row is kept, and nothing is created until you confirm the preview.

The import preview, showing what will be created, defaulted, and refused, with the file fingerprint
Fig 02 Workspace, import preview FY2026 NFR register, xlsx SHA-256 7f945ec6c076… Synthetic data
02Link

Connect each finding to the control it implicates

A rule-based linker proposes the control from reference packs derived from the FMR, FISCAM, and A-123 material. It is a lexicon rather than a model, and it proposes rather than decides. A person confirms, and the confirmation is what lands on the record.

A case record with its proposed control link awaiting a named person's confirmation
Fig 03 Case record fnd_appr0001 Proposed control link, unconfirmed Synthetic data
03Act

Run corrective actions to closure, and keep them closed

Root cause, plan, milestones, evidence, review, closure, sustainment, including reject and reopen. Every transition is guarded by role and appended to the trail with the person, the statement, and the time. Due dates come from a visible policy table, and a date a person set is never overwritten by a derived one.

A closed corrective action with its root cause, its state, and its closure package
Fig 04 Corrective action cap_wk000001, monthly bank reconciliations Closed, with its root cause and closure package Synthetic data
04Reconcile

Sort what changed into four piles

When a rescan comes back, results fall into four buckets: new, unchanged, reappeared, and absent. Absent proposes a closure. It never performs one. On the financial side, a five-rung ladder ties a balance to its support, and a difference that is not explained is displayed as unexplained rather than forced to zero.

Scan reconciliation with new, unchanged, reappeared, and absent counts
Fig 05 Scan reconciliation, two Nessus scans of one system SHA-256 08ed5f7c936b… 0 new, 325 unchanged, 0 reappeared, 69 absent Synthetic data
05Deliver

Hand over a package a reviewer can actually open

One ZIP with everything: records, embedded evidence bytes, human-readable reports, the full activity history, source provenance, the TraceSeal integrity manifest, OSCAL, eMASS, and ODCFO exports, the schema, and the stated limitations. Plus a single-file HTML reviewer package that needs nothing installed.

The exports list: the OSCAL POA&M, the eMASS CSV, the ODCFO CAP tracker, the submission package and the TraceSeal manifest
Fig 06 Deliver, exports OSCAL, eMASS, ODCFO, the submission package, TraceSeal Synthetic data

R.04 Compared, from their own documentation

What can a reviewer check without us?

That is the question a reviewer eventually asks. We compared Tracepoint against the GRC platforms, audit suites, and compliance tools a component would otherwise consider, using their own documentation and published catalog prices, and against the spreadsheets and shared drives most of this work runs on today.

Question
Tracepoint
Platforms and suites we examined
What can a reviewer check without us?
Every record, every evidence hash, the trail in order, and a root digest that any SHA-256 implementation recomputes. The package opens with nothing installed.
Access to the platform, or an export that carries what the platform chose to include. RegScale documents hash badges on evidence files; a package re-derivable without the vendor's software is not published by any platform we examined.
Can anything close on its own?
No. A scan that stops reporting a finding proposes a closure, and a named person confirms it on the trail, or it stays open.
Configurable. ServiceNow documents a stale-detection flow for vulnerabilities that can close on a schedule; the setting decides.
Where does it run?
In the browser on the unit's own machine. No server, no account, no network calls, and it keeps working with the network cable pulled.
Hosted services as the default, with on-premises editions documented by Archer and ServiceNow.
Who is it built for?
The person who holds the finding, at any scale from a single section to a headquarters.
The enterprise risk, compliance, or authorization office.
What does the reviewer need to open the output?
A browser. The reviewer package is one inert HTML file with nothing to install.
An account on the platform, or a generic export that has lost its lineage.
Is the price published?
Yes, on this site, with the unit defined. Three of the eight tiers fit on a government purchase card.
Mostly through GSA catalog listings: Diligent Audit Management at $29,100, Workiva at $31,294, Archer Incident Management at $96,219, Xacta 360 at $140,693 perpetual. Paramify alone publishes its own list, from $55,000 a year.
What does most remediation run on today?
Tracepoint replaces the assembly step that sits between the finding and the system of record.
Below the platforms, spreadsheets and shared drives. GAO-17-85, GAO-21-157, and GAO-24-106890 describe the result.

Catalog prices as retrieved 25 August 2026; the evidence-hash, on-premises, and stale-detection facts verified against vendor documentation on 29 September 2026. The full comparison, with sources and published prices.

R.05 The trail

Every action lands on a trail that only grows.

A change is a new row, never an edit. Each row carries the person, the role, the statement they made, and the time on their clock. The workspace's TraceSeal fixes all of it under one digest, and the rules for recomputing that digest are printed inside the artifact, so a reviewer can check it in ten years whether or not this company still exists.

Tracepoint says attested rather than signed, because a typed name on a holder-controlled machine is a management attestation and not a signature under FAR 2.101. It says append-only rather than immutable, because the application enforces the behaviour and the file system does not.

How the seal works, and what it does not prove

  • D. OkaforImported findings-fy26-q3.xlsx, 218 rows, 3 refused09:41
  • D. OkaforConfirmed control link FBWT-04 on FND-2026-11709:44
  • M. ReyesAttached reconciliation-2026-06.pdf, sha256 0de1…5a2510:02
  • M. ReyesAdvanced CAP-0417 to evidence-ready10:03
  • S. WhitfieldReviewed CAP-0417 and requested a second month of support14:20
  • S. WhitfieldSealed workspace, root digest recorded16:55
ROOT DIGEST 8365f63929f5cc9dbee1ef1e0b1e956d747d25c7b38ff8176cb959a492beb8d9

Names and rows above are illustrative. The root digest is a real TraceSeal value from a sample workspace. Brass marks the sealed record wherever it appears on this site.

R.06 The rules, printed

Every value a reviewer sees is the value the file contained.

These are the rules Tracepoint holds to, and every package states its own scope on its face.

A missing value is never invented

A fiscal year that is not in the file stays blank and is flagged as not provided. It is never filled with the current year and never displayed as though it were real.

A default always says it was defaulted

An unrecognised classification gets a default, and the record carries both the default and the original value the file contained.

An unexplained difference stays unexplained

The reconciliation ladder shows the gap. Nothing is forced to zero to make a screen look finished.

Conflicts are not resolved automatically

Two rows that disagree about the same finding are both presented. Tracepoint has no basis for choosing between two statements of fact and does not pretend to.

It does not judge evidence sufficiency

Whether a document proves a control operated is a reviewer's call. The product records what was attached, by whom, and its digest.

It does not close an auditor's finding

The NFR Database and eMASS remain the systems of record. Tracepoint is where the evidence behind a closure is assembled before it goes there.

R.07 Measured, on the shipping code

Ten thousand findings to a fifty-artifact package.

These runs use the product's own parser, its own guarded engine actions, and its own package builder on one laptop. Nothing is stubbed or estimated, and the datasets are generated from a fixed seed so the runs can be repeated. Ten thousand findings is three times the 3,322 findings GAO reported open across the Department at the end of FY2023 (GAO-24-106890).

7.5s10,000 findings to a 50-artifact package, one laptop, on each of three runs

MeasuredResultCondition
10,000 findings to a 50-artifact package7.5 sOne laptop, each of three runs; 10,000 of 10,000 rows created
10,000-line property book, import preview0.44 sFile fingerprinted, every conversion and gap listed before anything is created
Today screen on the full corpus1.0 sEvery screen inside its render budget
One finding, import to Reviewer Package export15 clicksPlus 3 file choices and one typed step name
Package restoreVerifiedA Full Export Package restores into a cleared workspace, checked against its TraceSeal manifest

10,000 of 10,000 rows created

Every row that should have become a finding did, on each of the three runs.

500 planted broken rows, handled by rule

23 refused with the reason, 28 blank fiscal years left blank and flagged, 37 defaulted and disclosed as defaulted, 33 duplicates named. The expected handling was written down before the run.

Exports checked before they save

The OSCAL POA&M export is validated against the NIST schema, and the eMASS export against the 21-column template, before either file saves.

Figures are from the filming build of the shipping code, run on one x64 laptop. The published performance report records the earlier 25 August 2026 run.

The full benchmark report

R.08 Where it runs

Nothing is hosted, nothing is transmitted, and there is nothing to authorize in the cloud.

No server, no account, no telemetry

The application is a set of files that run in a browser. Disconnect the machine and it behaves identically, because that is its normal mode. There is no listening port and no external connection.

Your own software approval, with nothing to send to FedRAMP

FedRAMP authorizes cloud services. Tracepoint has no cloud service, so there is nothing to authorize. A published integrity manifest lets your organization verify exactly which files it received before approving them.

The data is yours, without restriction

Every workspace, package, and artifact belongs to the organization. We receive no customer data because the product transmits none, and if a license ever lapses you keep a perpetual no-cost right to open and export your own work.

The security posture, the threat model, and the ten named threats

R.09 Pricing

One annual number per organization, in eight tiers that follow the echelons, with no per-seat fees.

Tracepoint has no accounts and no telemetry, so nothing is counted per person, and nothing leaves the machine to meter seats.

  • BrigadeUp to 50 organizations$62,500per year
  • InstallationOne base and every tenant on it, up to 300 organizations$195,000per year
  • CommandA division to a combatant command, up to 1,000 organizations$345,000per year
  • DepartmentOne military department, unlimited organizations$2,950,000per year
  • Department of DefenseThe whole Department, under the $5,000,000 sole-source ceiling$4,500,000per year

Every tier is the same software with support and updates included, and people, workstations, and records are never counted. The first three tiers are under the $15,000 micro-purchase threshold, and Command sits under the $350,000 simplified acquisition threshold. A&R Strategic Solutions, LLC, is an SBA-certified Service-Disabled Veteran-Owned Small Business (SDVOSB), certified August 2026, which supports a sole-source award up to $5 million where the conditions at FAR 19.1406 are met. The license unit, every entitlement, and every acquisition path.

R.10 The company

Built by people who have carried these findings.

Tracepoint is a product of A&R Strategic Solutions, LLC, an SBA-certified Service-Disabled Veteran-Owned Small Business (SDVOSB), certified August 2026. Its CEO is a veteran who saw these inspections from inside a unit, and its COO is a corporate executive of fifteen years fixing what audits find. The product exists because the assembly step, the part between the finding and the database, was always done by hand and always rebuilt from scratch when a reviewer asked.

Tracepoint is at Technology Readiness Level 6 under the DoD Technology Readiness Assessment Guidebook of February 2025, with a written threat model and independent verification ahead. It has been run end to end on real public audit data, measured at ten thousand findings, and every result is published on this site with the method beside it.

About A&R, and how a deployment runs

R.11 Next step

If this is a problem you own, we would welcome the conversation.

One reporting entity, its findings register, and its normal review chain is everything a deployment needs.