FUNCTION PROPOSAL & VALIDATION REPORT

Evidence
before claims.

Validate the function, review its business purpose, and check the source behind its answer.

9/9Contracts documented
9/9Current evidence records
OffAutomatic email delivery

Evidence state: current. Oct 27, 2026, 10:22 AM Central. This is a dated verification snapshot, not continuous monitoring.

The function
validator checklist.

  1. 01

    Function name

    A stable unique name maps to an actual implementation or is clearly labelled proposed.

  2. 02

    Business objective

    The function supports a stated outcome, without promising rankings, leads or revenue.

  3. 03

    Sample user question

    A realistic question explains why the function exists.

  4. 04

    Data source

    Fields, source authority, freshness and unavailable states are identified.

  5. 05

    API capabilities

    Existing endpoints and missing dependencies are distinguished.

  6. 06

    Input parameters

    Types, required fields, limits, conditionals and unsupported values are specified.

  7. 07

    Expected output

    Success, unavailable and disabled outcomes are defined.

  8. 08

    Permissions

    Read, navigation, draft and external-write boundaries are explicit.

  9. 09

    Verification evidence

    Dated results identify the tested contract; stale or missing evidence does not pass.

  10. 10

    Approval status

    Documentation does not grant provider access, model connectivity or permission to send.

The actual
test results.

FunctionAvailabilityContract / evidenceApproval status
Understand where the visitor isget_experience_contextAPI availableContract complete
Verified: ok
Read / navigation scope
Find homes using verified datasearch_propertiesNeeds property feedContract complete
Verified: unavailable
Provider approval needed
Read one verified homeget_property_detailsNeeds property feedContract complete
Verified: unavailable
Provider approval needed
Explain a featured communityget_area_contextAPI availableContract complete
Verified: ok
Read / navigation scope
Prepare verified homes for displaypresent_propertiesNeeds property feedContract complete
Verified: unavailable
Provider approval needed
Move to a useful part of the sitenavigate_experienceAPI availableContract complete
Verified: ok
Read / navigation scope
Compare verified property recordscompare_propertiesNeeds property feedContract complete
Verified: unavailable
Provider approval needed
Prepare a message for Michelleprepare_inquiryAPI availableContract complete
Verified: draft
Visitor reviews the draft
Automatic inquiry deliverysubmit_inquiryDisabledContract complete
Verified: disabled
Disabled by owner

Request and permission boundaries

Review the design
against the goal.

working

Local discovery has a public community source and allowlisted navigation actions.

Objective: local-discovery · Data: communities[]
waiting

The four property functions have code, but no live feed is connected. Unavailable responses are correct behavior, not verified property service.

Objective: verified-homes · Data: Authorized property feed
working

General inquiry preparation creates a reviewable draft. It does not send, store or enroll a visitor.

Objective: personal-contact · Data: Published business email and visitor draft text
off

Automatic inquiry delivery and scheduled email remain disabled by the owner’s instruction.

Objective: personal-contact · Data: emailPolicy
proposed

Journal read/search tools would connect the useful-content objective to a future guide. They are proposals, not callable functions.

Objective: useful-content · Data: articles[]
separate

API availability does not mean an LLM is connected. The local guide is deterministic; Michelle’s main Maya service is a separate system.

Objective: clear-capabilities · Data: Application routes and health response

CODEX PROPOSED FUNCTIONS

Useful next steps.
Clearly proposed.

These proposals come from the useful-content objective and existing data. They are not registered in the execution allowlist and cannot be called through the tool endpoint.

read_journal_article

Answer from a published Journal article

Let a future connected guide quote or summarize an approved article with its source links.

Business objective
useful-content
Data source & API capability
articles[].sections / sources. Existing article catalog; a dedicated model-callable read function is not implemented.
Input parameters
Article slug; optional question.
Expected output
Relevant passages or a bounded summary with the canonical article and primary-source links.
Permissions / approval
Read published content only. Proposed; not active.
Verification needed
Unknown slugs, source fidelity, dated advice, bounded output and linked article read-back.
find_local_read

Find the right local story

Help a visitor find a useful published read for their community or question.

Business objective
useful-content
Data source & API capability
articles[].title / category / summary / sources. Journal catalog is present; a dedicated guide search function is not implemented.
Input parameters
Community or topic; category; result limit.
Expected output
Published article matches with title, summary and canonical URL, or an honest no-match result.
Permissions / approval
Read published content only. Proposed; not active.
Verification needed
No fabricated articles, correct canonical URLs, category handling, empty results and relevance checks.
stage_journal_draft

Prepare an editorial draft for review

Support consistent local content through a reviewed draft workflow, without email or automatic publication.

Business objective
useful-content
Data source & API capability
Primary sources, article schema and existing topic catalog. No public draft-write API or editorial database is present in this copied app.
Input parameters
Topic, primary-source references, draft article and image provenance.
Expected output
A draft proposal and validation report; no publication or delivery claim.
Permissions / approval
Future authenticated editor-only write; not enabled. Proposed; not active.
Verification needed
Authenticated role, source and image checks, duplicate-topic check, article validation and durable review record before any future publishing integration.

What the evidence
verifies.

Contract fingerprint: 8d50fa7ef10aaaecfa93f0cc0b762d4af349ea08ce90212721733666df4c6452