Skip to main content
Continuous Evidence Ingestion

Turn everyday output into verifiable career proof

Sync PRs, commits, and design documents into an employee-private ledger. Review and approve structured impact metrics before anything enters your official record.

capture · pr-1842 → evidence.review
PDFPerformance rubricUploaded once, auto-parsedCSVWork history12 months importedSYNCYour toolsGitHub · Docs · Slack · JiraPerfolioTools connected · syncing liverubric.pdfhistory.csv
Live Evidence Ingestion Gate
acme/platform-core#1842 · Ingested from GitHub & Datadog
Pending Review Gate
Extracted Impact Metric

98% latency reduction (9s → 180ms P99) across 40M invoices. Dual-write migration cutover completed with zero downtime.

Grafana telemetry · Validated by Elena Rostova (VP Engineering)
Ledger: Approval required before record entry
THE WHY · PROBLEM 01: LOST

Your work gets lost within weeks of shipping.

AI made engineers 2–3× more prolific, but human memory didn't scale. Between the code you write and the credit you earn, your best contributions fade away before review night.

LOST

AI multiplied your output, not your memory.

  • Your work fades within weeks of shipping into production.
  • The evidence scatters across GitHub, Jira, Linear, and Slack threads.
  • You rebuild it from hazy recollection under tight review deadlines.
•Great work, quietly forgotten

The odds are bad. The cost is worse.

Numbers straight from empirical workforce research.

memory-decay · forgetting.curve
FADES WITHIN 24 HRS

Your Work Fades Fast

Ebbinghaus's forgetting curve, replicated in 2015 (Murre & Dros, PLOS ONE), shows people forget roughly 66% of new detail within 24 hours. Months later, over 80% of architecture nuances and SLA impact are gone.

focus-loss · interruptions.log
275PER DAY
1 EVERY 2 MIN

The Day Never Holds Still

Developers face an average of 275 focus interruptions per day (Mark et al., UC Irvine). Without continuous ingestion, high-impact contributions scatter across Slack channels, PR threads, and Jira tickets.

retention-gap · shipped.vs.remembered
87% CONTEXT LOSS

Only 13% Makes the Cut

Engineers ship an average of 48 substantive PRs, bug fixes, and architecture choices per half. Without continuous capture, fewer than 6 items (12.5%) survive into self-evaluations.

archaeology-tax · review-prep.time
14hLOST / CYCLE
14+ HOURS LOST

Review Prep Steals Two Full Days

Engineers spend an average of 14+ hours per review cycle digging through Git commits, closed PRs, and Slack threads to reconstruct what they shipped (State of Engineering Report). Automated capture reclaims that time completely.

THE MECHANICS · 3-STEP INGESTION

How raw code transforms into verifiable career proof

A disciplined, human-in-the-loop pipeline designed to capture real technical depth without creating manual work.

01SOURCE INGESTION

Sync PRs, Docs & Notes As You Build

Connect your GitHub, Linear, Jira, Slack, or terminal. Whenever you merge code, finalize an RFC, or receive peer kudos, Perfolio silently stages the work without interrupting your flow.

GITHUB · ACME/CORE #1842STAGED
feat: async partition router with zero-downtime shadow read
02METRIC EXTRACTION

Extract Hard Signal from Code Diffs

Perfolio's parser extracts quantified engineering impact: latency drops, throughput increases, cost reductions, and cross-team dependencies, stripping away irrelevant commit noise.

PARSED METRIC
9s → 180ms p99
RUBRIC MATCH
L6 · Core Systems
03HUMAN REVIEW GATE

You Control What Enters the Record

Nothing enters your permanent career ledger automatically. You review the extracted metric, refine the wording in seconds, and click Accept to cryptographically seal it.

✓ SHA-256 SEALEDEmployee-Private Ledger
CAPABILITY MATRIX · BUILT FOR ENGINEERS

Engineered for high fidelity and absolute privacy

Designed specifically for the nuances of modern software development workflows.

OMNICHANNEL INGESTION

Log from Anywhere Your Work Happens

Sync via GitHub PR webhooks, Linear tickets, Jira epics, Slack praise reactions (:memo:), Google Calendar design syncs, or the offline perfolio CLI directly from your terminal.

GitHubLinearJiraSlackCLI terminalGoogle Docs
ZERO-KNOWLEDGE SECURITY

Employee-Owned Encryption

Every record is sealed using client-side per-user encryption keys. Organization admins, managers, and HR systems cannot browse your private evidence ledger until you explicitly choose to share a report.

🔒 AES-256 GCM· Isolated per engineer
SMART NOISE SUPPRESSION

Automatic Chore Filtering

Perfolio automatically filters out automated Dependabot upgrades, minor documentation typo fixes, and routine lint commits so your ledger only reflects substantive engineering wins.

92 routine chores bypassed
8 high-signal architectural wins retained
TAILORED WORKFLOW · BUILT FOR YOUR LEVEL

How engineers capture impact at every stage

See how engineers use continuous capture to build an undeniable case for their next level.

SENIOR IC (L5) · Backend & Systems Engineer

Capture system latency and scale milestones

Senior ICs use Capture to preserve the quantitative proof of database cutovers, caching optimizations, and API refactors that otherwise get forgotten after the sprint closes.

EVIDENCE #E-9402 · BACKEND SYSTEMS
Distributed Shard Router Dual-Write Cutover
Successfully cut over partition table router across 40M shard rows. P99 query latency dropped from 9s to 180ms with 0 downtime.
Verified by Grafana Telemetry & GitHub PR #1842
01

What problem does Evidence Capture solve?

Most engineers forget 80% of what they ship within 3 months. When performance review season arrives, you are left scrambling through Git history, closed Jira tickets, and Slack channels. Perfolio captures the context, metrics, and technical design while details are fresh, eliminating end-of-year career archaeology.
02

What result will I receive?

A structured, searchable ledger of verified contributions. Each record includes a human-readable summary, quantitative impact metrics (e.g. 98% latency reduction), identified beneficiaries, and direct links to code pull requests or dashboard monitors.
03

How does it work with my inputs?

You can connect read-only integrations (GitHub, Jira, Linear, Slack), forward commit summaries, or simply type a quick 2-sentence note. Perfolio’s processing agent drafts a structured evidence item. Crucially, you review and approve every item before it enters your career record.
04

How does it connect to the rest of Perfolio?

Every accepted evidence item automatically feeds two systems: your Promotion Readiness rubric coverage (matching your contribution against specific ladder rows) and your 1-click Reports (generating promotion packets and Friday stakeholder updates).
05

What permissions, limits, and plan rules apply?

Individual records are strictly employee-owned and encrypted with per-user keys. Organization admins and managers cannot inspect your private capture logs. The Free plan includes manual capture, unlimited log entries, and basic connectors.
06

What should I do next?

Start by logging your latest substantive win or merged PR. Review the extracted metrics, accept the item, and see how it instantly strengthens your promotion ladder coverage.
Connected capabilities

Explore how the pieces connect

Every capability in Perfolio feeds into the same private, citation-backed career record.

perfolio · capture.sh
Get started

Put your engineering work on the record.

Start free as an individual engineer. Review every suggestion before it enters your record, and explore with sample data first.