Technical program and project portfolio · Cory Lintz

From complex requirements
to reviewable results.

I bring a program and operations background to independent software projects, with an emphasis on clear requirements, practical delivery plans, and evidence that supports the next decision.

My professional foundation includes 20 years of U.S. Air Force experience in IT modernization, operational test and evaluation, resource management, and workforce development. The projects below are independent work, separate from that employment.

My role centers on project ownership, requirements, direction, and review. Development includes AI-assisted implementation and review; these summaries do not imply sole authorship of every component.

Five projects. Clear delivery boundaries.

Explore the problem, my role, and the delivery decisions behind each project. Current status and remaining validation are shown alongside the work.

01 In development

Multi-platform delivery

Standing Order

Continuity information and offline access

An independent application project exploring how important continuity information can remain organized and usable across web and offline environments.

My role · Project owner: requirements, priorities, review, and development direction.

Status & limitsIn development. Cross-platform acceptance and recovery validation remain separate from code-level checks.

Read case study: Standing Order

The problem

A continuity tool has to remain understandable when access conditions change. That makes offline use, information organization, and recovery behavior separate requirements, not assumptions attached to a working interface.

Delivery approach

  • Organize delivery into distinct web, desktop, mobile, and validation workstreams.
  • Connect requirements to reviewable acceptance evidence and track dependencies between workstreams.
  • Distinguish source checks from runtime, device, and recovery testing.

Evidence & interpretation

The project has documented requirements, design decisions, a testing strategy, and recorded source-level verification checkpoints. The case study demonstrates delivery structure and evidence interpretation, not a completed release.

  • Requirements
  • Dependency management
  • Release criteria
  • AI-assisted delivery
02 Private prototype

Integration and traceability

MRDOTS Command Dashboard

Project visibility with evidence behind the status

A private prototype for bringing project status, source evidence, and bounded work coordination into one interface.

My role · Project owner: scope, constraints, priorities, review, and acceptance decisions.

Status & limitsPrivate prototype. Further integration and end-to-end acceptance remain under development.

Read case study: MRDOTS Command Dashboard

The problem

A dashboard can look complete while combining real source information, demonstration data, and capabilities that are still planned. Those differences need to be visible to support sound decisions.

Delivery approach

  • Map requirements to acceptance tests before treating a feature as complete.
  • Separate source-backed information from synthetic development views.
  • Review local candidate tests and hosted behavior as distinct evidence sets.

Evidence & interpretation

A private prototype and a versioned requirements-to-test mapping provide concrete material for reviewing scope and integration boundaries. Historical test reports apply to their tested candidates, not automatically to a later build.

  • Traceability
  • Integration boundaries
  • Acceptance testing
  • Technical communication
03 Local prototype

Desktop product development

MRDOTS Dictate

Local-first speech-to-text exploration

A Windows dictation project exploring push-to-talk input, local speech recognition, and an optional local text-cleanup step.

My role · Independent project owner, with AI-assisted implementation and review.

Status & limitsLocal prototype. Broad device compatibility, human-speech accuracy, and reliable text entry across third-party applications are not asserted here.

Read case study: MRDOTS Dictate

The problem

Dictation has to fit the flow of real work. Recognition, correction, application input, and installation each need evaluation; a successful transcript alone does not establish the complete user experience.

Delivery approach

  • Break the experience into capture, recognition, correction, and text-entry stages.
  • Explore user-controlled dictionaries, spoken commands, and text modes.
  • Use recorded fixtures and documented observations to distinguish tested behavior from remaining hands-on checks.

Evidence & interpretation

Project documentation records local builds, automated checks, and replay-based observations. The technical stack includes Tauri, Rust, React, and Whisper-based speech recognition.

  • User workflows
  • Desktop integration
  • Test design
  • Technical trade-offs
04 Public-facing project

Decision-support experience

PATH Discover

College degree and career exploration

A guided discovery tool that connects a person's interests and constraints with career pathways and related education options.

My role · Independent project owner, with AI-assisted development and human review.

Status & limitsAn exploration aid, not a validated prediction of career success, admission, earnings, or employment. Occupational figures have their own coverage and freshness limits.

Read case study: PATH Discover

The problem

Career exploration involves several kinds of information: interests, education requirements, work context, and labor-market data. A useful experience needs to make those relationships understandable without presenting a recommendation as a guarantee.

Delivery approach

  • Use an adaptive, one-question-at-a-time flow.
  • Keep pathway scoring deterministic and document how matches are produced.
  • Connect source-attributed occupational information with clear limits on its interpretation.

Evidence & interpretation

The project includes a documented scoring model, source and coverage notes, validation records, and a public-facing discovery experience.

  • Information design
  • Decision support
  • Data interpretation
  • Scope management
Explore PATH Discover →
05 Local build

Learning systems

MRDOTS Learning Platform

Learning progress grounded in an evidence log

An independent learning-platform project exploring adaptive practice, assessment workflows, and progress calculated from recorded learning activity.

My role · Independent project owner, with AI-assisted development and review.

Status & limitsLocal build. No claim of learner adoption, improved learning outcomes, accredited credentials, or production deployment.

Read case study: MRDOTS Learning Platform

The problem

A learning system can lose credibility when its progress display no longer agrees with the learner's answer history. Assessment rules and the source of each reported result need to be explicit.

Delivery approach

  • Derive progress and practice recommendations from recorded attempts and course content.
  • Separate changing learning estimates from completed assessment results.
  • Explore a course-grounded tutor and document the limits of assessment and mastery estimates.

Evidence & interpretation

Project documentation describes the learning engine, assessment rules, a sample course, and a historical local test and browser-review checkpoint. The repository describes a local build rather than a deployed service.

  • Evidence modeling
  • Assessment workflows
  • Product requirements
  • Learning technology

How I approach the work

Start with the decision

Define the user problem, the scope, and what evidence would make the next decision defensible.

Make dependencies visible

Separate workstreams and integration boundaries so progress in one area does not hide unfinished work elsewhere.

Match claims to evidence

Treat a design, a passing test, a local build, and an accepted release as different milestones.

Let's discuss the work.

For opportunities in technical program delivery, IT modernization, systems integration, or test and evaluation.

Get in touch →