Public methodology
This page explains what to trust, what to verify, and how to fix source-cited data without turning the main product flows into an operations manual.
An unofficial beta preview of a source-cited public intelligence layer for Texas innovation resources. It organizes allowed public sources into city pages, entity profiles, recommendations, data-quality signals, and governed correction paths.
Not an official state, city, Texas Venture Alliance, or Founders Arena product; not a complete Texas inventory; not a ranking system; and not legal, medical, financial, grant, investment, or eligibility advice.
Privacy boundary
The public data boundary keeps source-cited product fields visible while protected operator, owner, submitter, source-capture, and service fields are intentionally not exposed.
Stable public links, entity types, source references, confidence, freshness, and updated timestamps for published source-cited records.
Evidence decisions, source operations, merges, claim evidence, audit state, and private review metadata stay in the operator workspace.
Founder profile persistence, claim identity, correction submitter identity, and recommendation profile links are not exposed through anonymous public browsing.
Public responses exclude these details even when related records exist in protected review and source-capture work.
Contract fields tracked: 10
Governance
Source tiers make evidence quality visible without implying official endorsement.
Government, university, program, event, or organization pages controlled by the source owner.
Direct public pages from the named organization, event host, fund, accelerator, lab, or program operator.
Public news, ecosystem publications, partner pages, or announcement pages that cite a source but are not the owner page.
User-submitted public candidates that still require evidence review before they affect public records.
Sources with incomplete trust metadata. These should be reviewed before they support recommendations or presentation claims.
Source categories
These are the public source categories the current source registry and source submission workflow understand.
Pages controlled by the source owner for an ecosystem resource, program, organization, or event.
City, chamber, innovation district, or economic development pages that describe local ecosystem resources.
Technology transfer, entrepreneurship center, commercialization, lab, or student venture pages.
Accelerator, incubator, venture studio, cohort, application, or mentor program pages.
Allowed public event calendars, event host pages, or registration pages.
Public source evidence used to support source-cited records.
Grant, challenge, open call, competition, or public funding opportunity pages.
Investor organization, angel network, public fund, or portfolio pages.
Coworking, wet lab, maker space, innovation district, or facility pages.
Public partner, sponsor, member, or ecosystem directory pages with reviewable listings.
Public source candidates submitted by users and held for evidence review.
Pipeline
The graph favors reviewable source evidence over unsupported claims.
Sources must be public, relevant to Texas innovation, allowed by crawl policy or marked manual-only, and useful for organizations, programs, events, opportunities, investors, spaces, university resources, city coverage, or source-quality review.
Deterministic parsers and structured extraction produce candidate entities and assertions. Material facts need a source URL, extraction method, confidence score, and extracted-at timestamp before they can support public profiles.
Candidates are compared by canonical URL, domain, normalized name, city, address, parent organization, source overlap, and review signals. Ambiguous matches stay in review instead of silently merging.
Confidence is a review signal, not a public ranking. High-confidence records can still be corrected, medium-confidence records should carry caveats, and low or missing confidence records need verification before routing.
Each source has a refresh policy. Records can be fresh, due soon, stale, or unknown; stale records are visible as data-quality signals and should not drive recommendation or outreach claims without verification.
Stale events, deadlines, closed programs, and unsupported claims are flagged, deprioritized, hidden from default routing, or held for correction/review when their source evidence is no longer current.
Recommendations are generated from deterministic fit signals: city/region, sector, stage, needs, audience, status, source freshness, confidence, eligibility caveats, and public action URLs. The platform explains why a result matched and cites the underlying source references.
Corrections and claims
Human correction and owner review are part of the product, not a support afterthought.
Anyone can report inaccurate, stale, duplicate, missing, or removal-requested data. Corrections enter evidence review and do not update public records automatically.
Open pathOrganization or program owners can request a claim with signed-in identity and public verification evidence. A claim does not grant permissions until reviewed.
Open pathUsers can submit public source candidates for missing city categories, stale records, or stronger evidence. Submission does not make a city complete.
Open pathPublic sample
This public sample is loaded from reviewed public records so the methodology page reflects the same public sources used by public pages.
City or economic development page / official
City or economic development page / official
City or economic development page / official
City or economic development page / official
City or economic development page / official
City or economic development page / official
City or economic development page / official
City or economic development page / official
8
Source records
5
Trust tiers
11
Source categories