Decide and build

The decision is a person’s, and the record proves it

  1. The problem

    Deciding to pursue funding commits real staff time. AwardBase treats that as a consequential act: a human capability, against an exact eligibility position, recorded with the authority that permitted it.

  2. What the system contributes

    It reads the sources, extracts what they require, and keeps every derived figure attached to the record it came from — so a number can be checked rather than trusted.

  3. What a person decides

    Every consequential act here is a named human decision, bound to the exact version it was made against. The system prepares it; it never takes it.

Decision

  • Human go/no-go

    Built

    A model may recommend and can never decide. The decision requires a human actor holding an exact-record capability, and the system refuses a model execution context holding the same grant.

  • Changed since review

    Built

    If the eligibility position moves after a decision, the decision is reported as changed rather than quietly standing.

Proposal

  • Requirement matrices

    Built

    Requirements extracted from the solicitation with citations back to the document, and a review state so nobody mistakes an extraction for a reading.

  • Approved facts

    Built

    Narrative content is assembled from facts a person approved. A claim with no approved fact behind it cannot be generated into a proposal.

Pursuit and proposal intelligence · AwardBase