Policy Graph
The Apogee Policy Graph - the official record and your own working knowledge, connected in one compounding graph that makes every feature sharper the more you use it.
Policy Graph
The Policy Graph is the engine underneath everything in Apogee. It has two layers: a shared layer built from the official record, and a private layer built by you, from your own work. Every feature reads from both.
The official record layer
Apogee continuously ingests the official record - bills, hearings, votes, members, committees, lobbying disclosures, PAC contributions, regulatory filings, policy news - and connects it into a knowledge graph of 200K+ entities and their relationships. Who sponsored what, who testified where, which PACs fund which members, which firms lobby which bills. This layer is the same for every user, kept current every day.
Your private layer
The second layer is yours alone, and it starts empty. As you work, Apogee deposits what you do into a private graph connected to the official record:
- People you track - contacts, enriched from the official record, with every call and meeting you log (People)
- Positions you count - whip counts and how each office moved over time (Whip)
- Commitments you owe - follow-ups and deadlines, anchored to the bills that drive them (Chase)
- Topics you watch - folios, watches, and the briefings they generate (Folios, Briefings)
- Context you accumulate - your role, your organization's positions, uploaded files, and saved analyses (Memory)
Why it compounds
Each layer makes the other more useful. A contact in your graph is not just a name - it is connected to the member they staff, the bills that member sponsors, and the hearing on Thursday. A commitment is not just a to-do - it moves when the markup it depends on moves.
The result is a flywheel: the more you work in Apogee, the more your graph knows, and the sharper every answer, briefing, and reminder becomes. Your Policy Graph is the version of Apogee that only exists for you - and it cannot be bought off a shelf, because it is built from your own work.
Privacy
The private layer is private in the strict sense: it belongs to your account, it is never shared with other users, never aggregated across customers, and never used to improve anyone else's results. On Teams and Enterprise plans, only what you explicitly place in shared memory is visible to teammates - your contacts, interactions, and whip positions stay yours. See People privacy for details.