Jason V. Holmes
Back to portfolio

Requirements engineering / applied research

Federal Submittal Compliance Model

Make obligations traceable from the first requirement to the evidence that closes them.

Deployed instrument · Preliminary, single-organization observations

Research snapshot11 Sep 2026

Line-item first-pass approval

69%

20 first-pass approvals / 29 dispositioned line items

Different units. Not a performance trend.

01 / the engineering problem

An obligation is more than a checkbox.

A small subcontractor must track preparation, prime routing, government review, evidence, deadlines and approvals that can expire. The public model documents a deployed instrument in one organization, while keeping operational records private.

61

Baseline gates

Six phase bands structure the baseline. Project instances vary from 60 to 72 rows with conditional scope.

11

Lifecycle states

Preparation, routing, adjudication, closure and expiry each retain meaning and evidence guards.

01

Operating context

Preliminary observations from one organization. No control group or causal effect established.

02 / traceability in motion

Follow the obligation, preserve the evidence.

  1. PrepareOwner + requirement
  2. Prime reviewRouting evidence
  3. SubmitTransmission record
  4. AdjudicateDecision artifact
  5. Close / renewDischarge + validity

Simplified explanatory path through the 11-state model. Rejection and renewal loops remain in the source specification; this is not a live instrument view.

03 / explore a dependency

What if access arrives after the deadline?

A site-dependent submittal can be due before its prerequisite is available. Move the access day to see the timing relationship. This synthetic example assumes a deadline of award + 30 calendar days and zero preparation time after access.

A negative margin identifies a conflict under those assumptions. A nonnegative margin does not establish practical feasibility, contractual compliance or an approved remedy.

Timing conflict: access arrives 10 days after the due date.

Synthetic illustration · calendar days · not operational data

04 / measurement discipline

Keep the denominator attached.

The 11 September 2026 snapshot reports 20/29 first-pass approvals by dispositioned line item and 8/17 by package. A package can contain several line items. The switcher above changes the analytical unit, not the time period.

The dashboard's 85% current-state gate share answers a different question. Superseded and earlier gate-row percentages are not combined into an improvement claim.

What the evidence supports

Sanitized architecture and bounded aggregate observations. Raw operational data are not public; this review did not independently reproduce the measurements. No population-wide result, causal improvement or established scholarly novelty is claimed.

05 / authorship and next work

Build the research on a traceable foundation.

Independent work by Jason V. Holmes, published under CC BY 4.0. No employer, university or government endorsement is claimed. Literature review comes before expanded taxonomy or stronger novelty claims; independent coding and a broader comparative design remain research work.

Systems, evidence, iteration

Have a problem that needs a system?

I connect requirements to models, interfaces and evidence, using AI-assisted implementation under human review.

Start a conversation

Portfolio review: 17 November 2026.