Precon Portal Acquisition Workflow

Summary

Portal acquisition turns invitation links and portal observations into reviewable source state. It determines which portal source is effective, when authentication is required, which files are available, and which source should be preferred before publication.

The concept page Precon Portal Acquisition orients the primitive. This thread frames portal work as a workflow with preview, acquisition state, verification, review, and repair.

Reader Question

How does Precon use portal evidence without letting browser or provider behavior become hidden business logic?

Surface Or Workflow

Operators see portal acquisition in opportunity detail, portal review sections, manifest editors, readiness disclosures, and auth-required runbooks. Engineers enter through portal link extraction, source assessment, acquisition preview, verification, history repair, follow-on services, and portal crawl jobs.

Lifecycle

Intake extracts portal links from messages or manual evidence. Portal services rank and assess the links, preview acquisition when possible, record manifest state, and surface authentication or ambiguity as reviewable issues. Once a portal source is accepted, publication services can decide which documents to copy into opportunity-owned storage.

Repair is first-class because portals are unstable: credentials can expire, links can point to sibling projects, manifests can conflict, and document sets can change after the initial invite.

Child Threads

Implementation Boundaries

Portal capability packages live under services/precon/portals, including links, acquisition, acquisition state, source assessment, verification, document observation, publish, follow-on, and history repair. Thin entrypoints under jobs/precon preview acquisition, crawl sources, select links, verify links, and repair historical state.

Tradeoffs

The portal workflow is explicit because it is tempting to treat browser automation as a side task. Precon instead records acquisition and manifest state so operators can explain what was observed, what was published, and what still needs credentials or repair.

Visual

The current visual is a graph neighborhood. The intended visual is a portal state diagram from extracted link to source assessment, acquisition preview, manifest review, authentication issue, publication, and repair.

Source Evidence

  • docs/engineering/concepts/precon-portal-acquisition.md
  • services/precon/portals
  • services/precon/intake/portal_links
  • services/precon/review/portal_review.py
  • jobs/precon/preview_portal_acquisition/run.py
  • jobs/precon/crawl_portal_sources/run.py
  • jobs/precon/select_primary_portal_links/run.py
  • docs/runbooks/precon-portal-auth-required.md
  • tests/precon/test_portal_acquisition_manifest.py