Skip to content

Instantly share code, notes, and snippets.

View Silverstar187's full-sized avatar

Silverstar187

0 followers · 6 following
View GitHub Profile
@Silverstar187
Silverstar187 / leads-status-design.md
Created May 7, 2026 11:24
Leads-Stack: Status Quo + Design (Issue #9 LLM-Postfilter, #11 Intent-Signals, #3 Pipedrive, #5 Fireflies)

Leads-Stack: Status Quo + Design

Stand 2026-05-07. Sales-Engine. Bezug: Issues #9 (P0), #11, #3, #5.

Status Quo

Komponenten live

@Silverstar187
Silverstar187 / onboarding-status-design.md
Created May 7, 2026 11:24
Onboarding-Stack: Status Quo + Design (state-sync + user-edit-lock)

Onboarding-Stack: Status Quo + Design

Stand 2026-05-07. Sales-Engine. Bezug: Issue #8, #34, Hormozi-Patch.

Status Quo

Komponenten live

@Silverstar187
Silverstar187 / restructure-proposal.md
Last active May 7, 2026 10:38
Sales-Engine Onboarding Restructure Proposal — Konrad Lübeck Review 2026-05-07

Sales-Engine Onboarding — Strukturierungs-Vorschlag (v5)

Aggressive Reduktion 95→55 (Konrad-Sales-Sicht + Web-Crawl/LinkedIn-Inferenz für NICE-Felder). v5 (2026-05-07): Anbieter-Namen neutralisiert (Issue #4) — Drittanbieter-Tools nun als generische Outreach-Plattform / Web-Crawl / Workflow-Engine bezeichnet. Update 2026-05-07 (v4): Quelle/Bemerkung-Daten aus alten Tabellen in <details>-Blöcke der effective_fill-Sektion migriert. Tabellen Sek 1/2/3 bleiben kompakt. Coverage erweitert von 10→54 Detail-Blöcken. v3 (2026-05-07): Sektion 1 17→10 · Sektion 2 33→29 · Sektion 3 35→15 · STRIP 19→51. Vorgänger v2: Hormozi-100m-Offer-Felder ergänzt + effective_fill in eigene Sektion ausgelagert. Basierend auf Konrad Lübeck's Live-Review im Meeting 2026-05-06 (148min) Erstellt: 2026-05-07 · Review von: Konrad Lübeck Quell-Schema: frontend/briefing-fields.json v1.1.0 (95 Felder, 15 CRITICAL / 23 IMPORTANT / 57 NICE)

@Silverstar187
Silverstar187 / p2ai-vs-security.md
Created May 7, 2026 01:09
p2ai vs macOS `security` — feature comparison + roadmap

p2ai vs macOS security — feature comparison + roadmap

Application goal

p2ai is a credential gate for the AI-agent workflow on macOS.

Single user, single Mac, single source of truth for secrets that AI agents (Claude Code, Cursor, Aider, etc.) need to fetch without leaking them into chat transcripts. Touch-ID gates every fetch; the agent-cache reduces friction; p2ai run injects values into a child process's environment without ever touching stdout, disk, or the parent shell.

Not in scope: team sharing, multi-device sync, GUI form-fill, SSH-key management, generic password-manager features. Use 1Password / Vault / pass / Bitwarden for those.

@Silverstar187
Silverstar187 / p2ai-env-bundle-design.md
Created May 7, 2026 01:02
p2ai env-bundle storage — design exploration (WIP) for issue #5

p2ai env-bundle storage — design exploration (WIP)

Status: half-baked / brainstorming. Linked from Silverstar187/passwort2ai-by-fingerprint#5.

The question

When importing .env files into p2ai, what's the right storage shape?

Approach A — split: each VAR is its own kdbx entry