What Proofline is for
Proofline is being built for moments when losing the record could matter. It helps preserve end-to-end encrypted evidence as events unfold, while giving trusted contacts controlled access when it matters.
Some moments are hard to reconstruct later: an unsafe situation, an important interaction, a missed check-in, damage, harassment, threats, or a dispute. Phones break, platforms vanish, people get pressured, and institutions have an impressive talent for asking vulnerable people for perfect records after chaos.
The goal is not to turn every record into an emergency. The goal is to help a person preserve evidence, control who can access it, and avoid depending on a single fragile device as the only copy of something that may later matter.
Planned future structure
Proofline's politics are not a sticker on the README. They should shape the structure: open source, self-hosting, worker compensation, anti-surveillance design, and governance that makes capture harder.
Proofline is aligned with cooperative and libertarian socialist principles: workplace democracy, public-good infrastructure, transparent compensation, and pay for labour rather than ownership extraction. Public-good infrastructure should not quietly mutate into a trust-branded SaaS funnel.
The planned long-term direction is a non-distributing cooperative or similar mission-locked public-good structure. If the project reaches that stage, governance, worker compensation, and surplus use should be aligned with the project's public-interest purpose.
Values should shape the structure, not sit around like a decorative HR fern. For Proofline, trust is organizational as well as technical.
Proofline should serve users and aligned communities, not become a private extraction machine.
Future governance should support workplace democracy, transparent compensation, and shared accountability.
Founder or director compensation, if it happens, should pay for defined labour, not equity, dividends, or ownership returns.
Surplus should go back into Proofline, contributors, security reviews and audits, infrastructure, documentation, public-good deployments, related tooling, and smaller aligned projects.
The structure should make mission drift, vendor lock-in, and corporate capture harder, not merely better branded.
Self-hosting and open source are part of resisting platform dependency and surveillance-capitalism gravity.
SaaS goblin containment
Proofline is unlikely to respond to unsolicited sales pitches, outsourcing offers, SEO packages, lead generation offers, growth hacking, AI automation stacks, blockchain strategy calls, quick 15-minute vendor emails, or recurring SaaS tools looking for a problem to attach themselves to.
| Email phrase | Likely outcome |
|---|---|
| "Quick 15-minute call" | Archived |
| "Scale your startup" | Archived harder |
| "AI-powered growth" | Sent to the goblin pit |
| "Blockchain strategy" | Salt circle applied |
| "AI blockchain growth strategy" | Vatican contacted |
| "Synergy" included too | Domain exorcism considered |
| "Automate outbound growth" | Goblin containment protocol activated |
| "Targeted lead lists" | Added to the cautionary exhibit |
| "Finding people who actually need it" | Founder insecurity lure detected |
| "Following up in case this slipped through" | It did not. Archived again. |
| "Personalized outreach at scale" | Harassment, but make it scalable |
If Proofline needs a service, it will be evaluated through project needs, privacy requirements, security boundaries, governance, maintainability, and public-interest fit. Unsolicited vendor outreach is unlikely to receive a response.
Proofline is experimental, not an emergency service, and not a guaranteed real-time response system.
Production mobile capture, trusted-contact notifications, official hosted accounts, cost-recovery billing, live context sharing, and decryption workflows are not production features today.
These project documents provide more detail about the current implementation, planned work, and security limits.
