1. Purpose of This Document

This document establishes California as DARS Pilot 1.0 — the first intentional, documented institutional deployment of the Digital Adoption Resource System. It defines Phase I scope, learning agenda, documentation commitments, and success markers so that twelve months of operation produce a credible operational record rather than simply a populated set of state pages.

The pilot is designed to serve three audiences simultaneously: (1) internal product and protocol development; (2) prospective institutional partners (universities, foundations, adoption professionals, and government contacts); and (3) future readiness for competitive federal or philanthropic support. It is not a grant application.

2. The Problem and the DARS Thesis

Adoption-related information in the United States is fragmented across state agencies, private providers, national organizations, legal resources, and informal networks. Families, professionals, and advocates routinely encounter incomplete coverage, outdated materials, inconsistent terminology, and no reliable single starting point. The result is friction, duplicated effort, and unequal access depending on geography and digital literacy.

DARS was conceived to address this structural information problem. The system is being built as a centralized, state-aware resource framework that organizes adoption-related information by topic, jurisdiction, service type, and user pathway. The design prioritizes accuracy, currency, clear navigation, and the ability to surface both resources and gaps.

Critically, the DARS concept predates the current federal funding opportunities that now describe many of the same structural needs — data standards, interoperability, technology infrastructure, measurable outcomes, cross-jurisdiction coordination, and national dissemination. Federal priorities are independently moving toward solutions that align with the problem DARS was created to solve. This sequence is intentional and should be preserved in all external messaging.

3. Why California as Pilot 1.0

California offers a rigorous and representative first environment for several reasons:

• Scale and complexity. Large population, high volume of foster-care and private adoptions, and a county-administered child-welfare system create meaningful variation within a single state.
• Institutional density. Presence of public adoption agencies, private licensed agencies, Adoption Service Providers, post-permanency programs, universities, and professional associations supplies both content partners and future evaluators.
• Documented system activity. Ongoing modernization efforts (including CWS-CARES) and established programs such as the Adoption Assistance Program and Resource Family Approval process provide concrete policy and data reference points.
• Dissemination potential. Lessons and protocols developed in California can be adapted for other large and mid-sized states without starting from zero.

Treating California as Pilot 1.0 rather than a generic content rollout shifts the objective from “populate pages and generate traffic” to “operate a documented institutional pilot that produces methodology, data, professional network, and learning.”

4. Phase I Objectives (12-Month Horizon)

Phase I has five primary objectives:

• Resource architecture. Establish a stable, reviewable taxonomy and California resource inventory covering major adoption pathways (foster-care adoption, private/domestic, intercountry, adult adoptee, birth-parent, and post-permanency support).
• Accuracy and currency protocols. Implement repeatable processes for source verification, update cycles, and gap flagging so that the California presence remains trustworthy under operational load.
• Professional participation. Recruit and document a working network of California adoption professionals, agencies, and subject-matter reviewers who contribute to content quality and protocol refinement.
• User pathway observation. Capture how real users (prospective adoptive parents, professionals, and others) move through the system, where friction occurs, and which pathways are incomplete or missing.
• Institutional record. Produce a 12-month pilot report containing methodology, coverage metrics, gap analysis, protocol versions, network description, and early outcome indicators suitable for external partners.

5. Documentation and Learning Agenda

From day one, the pilot will systematically record the following categories. These become both internal development signals and the evidence base presented to partners twelve months later.

6. Alignment with Emerging Federal Priorities (Benchmark, Not Origin)

Recent Administration for Children and Families (ACF) / Children’s Bureau activity — including technology-focused Notices of Funding Opportunity and Requests for Information related to child-welfare system modernization, adoptive family recruitment and matching, data standards, and interoperability — describes many of the same structural needs that DARS was designed to address: technology infrastructure, common data approaches, measurable outcomes, cross-jurisdiction coordination, and scalable dissemination.

This alignment is treated as independent third-party validation of the problem diagnosis, not as the reason DARS exists. The pilot will periodically compare its architecture, documentation practices, and outcome orientation against the federal framework as an external quality benchmark. The comparison is diagnostic, not compliance-driven. DARS will not be redesigned solely to fit any single funding opportunity.

Messaging to partners will remain precise: “We developed DARS around a problem recognized for years. Federal priorities are now independently moving toward many of the same solutions.” No public implication of federal endorsement or grant dependence is appropriate or intended.

7. Phase I Work Plan Outline

The 12-month period is organized in three overlapping stages. Exact calendar dates will be set once internal capacity and initial partner conversations are confirmed.

Stage A — Foundation (Months 1–3)

• Finalize California taxonomy and priority pathway coverage map.
• Stand up version-controlled accuracy and update protocols.
• Complete initial high-priority resource inventory and verification.
• Identify and invite core professional reviewers / advisors.
• Establish baseline metrics dashboard and documentation repository.

Stage B — Operation & Observation (Months 3–9)

• Maintain and expand California resource coverage under live protocols.
• Log gaps, user pathway friction, and professional feedback on a rolling basis.
• Iterate protocols and information architecture based on observed data.
• Deepen professional network and document contribution patterns.
• Conduct at least one structured mid-pilot review against the documentation agenda.

Stage C — Synthesis & Institutional Record (Months 9–12)

• Compile 12-month pilot report: methodology, coverage and accuracy metrics, gap analysis, protocol versions, network description, user-pathway findings, and early outcome signals.
• Produce a concise external brief suitable for universities, foundations, agencies, and professional associations.
• Identify Phase II priorities (additional states, deeper outcome measurement, or specific interoperability experiments).
• Preserve the federal NOFO/framework comparison as part of the institutional record for future reference.

8. Success Markers at Twelve Months

Phase I will be considered successful if the following are true:

• A documented, version-controlled set of California resource protocols exists and has been operated for at least nine months.
• Coverage and gap analyses are available for the priority pathways and can be shown to external parties.
• An identifiable professional network has contributed review or content and can be described with roles and contribution types.
• User-pathway observations have produced concrete, prioritized improvements to navigation or content.
• A 12-month pilot report and short external brief exist that present DARS as a functioning pilot with methodology and data, not merely a concept.
• The institutional record clearly preserves the independent origin of DARS relative to federal funding opportunities.

9. Strategic Positioning Statement

Twelve months from launch, conversations with universities, foundations, government agencies, or future grant reviewers will not rest on an idea. They will rest on a functioning pilot, its data, its methodology, its professional network, and what was learned by operating it. That is a materially stronger foundation for whatever comes next — including, if later chosen, pursuit of federal or other institutional support.