{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:administrative-services-managers-policy-manual-update:t-td:v1","lens":"ManagedWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":1,"C7_magicLensFit":1,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/administrative-services-managers-policy-manual-update","stableHash":"wcc:administrative-services-managers:policy-manual-update:document:v1"},"problem":{"slotStatement":"When the board amends a policy (say Policy 210 on credit and collections), the Admin Services Manager edits the Word master on a shared drive, emails redlines to department heads, and manually re-issues binders — but three months later nobody can prove which version of Policy 210 was in force the night a disputed service disconnection happened, and the RUS auditor's provenance question sits unanswered for weeks."},"approach":{"oneSentence":"A board-resolution-linked policy register that ingests each approved motion from the board packet, redlines the affected manual sections against the prior in-force version, routes department-head acknowledgements with timestamps, and issues a dated, board-minute-cited manual edition that any auditor or member can trace back to the exact meeting that enacted it."},"customer":{"icpShape":"The General Manager / CEO at a member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative) in the 15k–150k meter band, where the buyer is the GM/CEO (who signs the software PO and answers to the elected board for RUS and NERC/FERC posture) and the daily user is the Administrative Services Manager or Corporate Secretary who maintains the Board Policy Manual and Section 7/Section 9 administrative policies.","beachheadShape":"EarlyMajorityWorkflow: Touchstone Energy / NRECA-affiliated distribution cooperatives with 20–60k meters that just completed an RUS Form 7 audit or a board-ordered policy refresh and have a standing Policy Committee cycle."},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-MarketplaceClearing","beachhead":"EarlyMajorityWorkflow: Touchstone Energy / NRECA-affiliated distribution cooperatives with 20–60k meters that just completed an RUS Form 7 audit or a board-ordered policy refresh and have a standing Policy Committee cycle.","competitors":{"substitutes":[{"name":"Network drive / SharePoint folder holding the Word master and PDF binders","category":"manual-bridge","uncopyabilityReason":"A folder is not a product; it has no enactment chain, no in-force-on-date query, and no acknowledgement ledger — it is the pain, not a competitor."},{"name":"NISC iVUE Connect (policy and board-packet modules)","category":"incumbent","uncopyabilityReason":"NISC is a cooperative-owned CIS/accounting core whose roadmap is governed by a member ballot and multi-year release train; bolting a resolution-to-policy provenance engine onto iVUE requires touching the board-packet module, the document repository, and the member-portal notification layer simultaneously — integration depth across three regulated modules that NISC ships on an 18-month cadence, not six months."},{"name":"BoardDocs (Diligent Community) used for board packets and meeting minutes","category":"incumbent","uncopyabilityReason":"BoardDocs is a meeting-workflow product whose data model ends at the approved minute; it has no representation of an 'in-force manual section' or a department-head acknowledgement ledger, and its SOC2-scoped multi-tenant SaaS deployment cannot absorb a cooperative's on-prem Word/PDF manual corpus without a deployment-mode rebuild away from its K-12/municipal template library."},{"name":"PowerDMS (NEOGOV) policy management","category":"incumbent","uncopyabilityReason":"PowerDMS owns the law-enforcement and healthcare accreditation corpus (CALEA, DNV) and its distribution channel, pricing, and content library are tuned to those verticals; it lacks the NRECA/RUS policy taxonomy, the Section 7/Section 9 bylaw structure, and the Form 7 audit hooks, and rebuilding that vertical-data corpus and cooperative sales motion is a multi-year commitment against its core verticals."},{"name":"ChatGPT Enterprise used ad-hoc by the Admin Services Manager to summarize redlines","category":"AI-native horizontal","uncopyabilityReason":"A horizontal LLM has no liability posture for 'this is the policy that was in force on 2024-11-12' — it cannot be deposed, cannot sign an RUS auditor's attestation, and OpenAI's product shape deliberately avoids the regulated-record-of-authority liability that a cooperative's board minutes demand."}]},"studioThesis":"T-TD","killThreshold":{"K":11,"M":80,"N":7,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Enactment linkage (free-text document store ↔ every manual section hard-linked to the board resolution and meeting minute that enacted it)","yAxis":"In-force-on-date query (latest-version-only ↔ point-in-time reconstruction of the full manual as of any historical date)","winningQuadrant":"Every policy section hard-linked to its enacting board motion, with point-in-time reconstruction so an auditor or member can pull 'the manual as it stood on 2024-11-12 at 19:00 CT'","loservilleEscape":true,"loservilleQuadrant":"Free-text Word masters on a SharePoint folder showing only the latest version — the exact failure mode BoardDocs and the shared-drive bridge exhibit when an RUS auditor asks which credit-and-collections policy governed a disputed November disconnection"}},"unmetRequirements":[],"pricingArchitecture":"tiered"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/administrative-services-managers-policy-manual-update","thesis":"https://api.sb/v1/theses/T-TD"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575ac8efc690ce","edgeLocation":"a0575ac8efc690ce","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1/references"},"items":[]}}