Skip to main content

Handover

Feature and configuration status

This page states plainly what works, what needs credentials, and what has not been validated. Toolkit version 0.1.0-draft.

This is a prototype build

Prototype build. Not community-validated, field-tested, endorsed or certified. Content is either platform documentation or clearly-labelled synthetic demonstration data. Do not present it as validated production software, and do not describe any output as community-approved.
Module status

Accounts, roles and memberships

Implemented

Email/password and Google sign-in, profiles, community memberships and five roles. Row-level security enforces every read and write.

Resource library and approval workflow

Implemented

Catalogue with categories, tags, attribution, sensitivity classification, audiences, AI permission, version history, review dates, draft/review/published/revoked states.

Field monitoring forms

Implemented

Five configurable templates with typed fields, units, validation, photos, drafts, edit history and location-privacy controls. Templates are configurable forms, not certified protocols.

Offline field mode

Implemented

Observations and photos queue in the browser database, sync once using idempotency keys, and surface conflicts for you to resolve. Restricted resources are never cached unless the owning community permits offline retention.

AI knowledge assistant

Needs configuration

Retrieval and citation logic run on the server against approved, AI-permitted resources. Answer generation needs the platform AI key to be present; without it the assistant reports a setup-required state instead of inventing answers.

Monitoring dashboard

Implemented

Counts, trends, completeness and coverage computed from submitted observations you are permitted to see. Sensitive and culturally sensitive locations are excluded from coordinate display.

Printable toolkit and PDF export

Implemented

Builds a cover, contents, resources, blank monitoring forms, safety checklists, glossary and citations. Restricted content is excluded by default.

Distribution plan records

Implemented

Administrators record audiences, partners, channels, owners, release dates, accessibility formats and delivery confirmation, and export CSV or PDF. No delivery record exists unless a person enters it.

Field testing and report generator

Implemented

Test sessions, testers, scenarios, device and connectivity details, usability ratings, defects and resolution status. Reports summarize only recorded activity and are marked draft until sessions are completed.

Live weather and marine conditions

Needs configuration

No weather or marine data provider is connected. The ocean safety module links to named public services and shows an unavailable state rather than displaying unsourced conditions.

Community validation and field testing

Not implemented

No community has reviewed, authorized or endorsed this build. No field testing, accessibility audit or certification has been completed.

Traditional Ecological Knowledge content

Not implemented

No TEK is present. The single TEK entry is an unpublished, labelled placeholder awaiting community authorization.

External credentials
CredentialNeeded forStatus
Platform AI keyAI assistant answer generationManaged by the hosting platform. Stored server-side only; never exposed to the browser.
Google sign-in credentials (optional)Branded Google sign-inManaged credentials are used by default. Supply your own client ID and secret in the backend auth settings for your own branding.
Weather / marine conditions API keyLive conditions in the ocean safety moduleNot configured. Until a provider and key are supplied, conditions are shown as unavailable with links to public services.
Email sender domain (optional)Branded confirmation and reset emailsDefault platform sender is in use.
Administrator setup steps
  1. Create an account, then have an existing platform administrator grant your role.
  2. For the very first administrator, assign the platform_admin role to your user in the backend membership table, then sign out and back in.
  3. Replace the demo organizations with real organizations and communities before inviting anyone. Demo rows are flagged and can be removed together.
  4. Review every resource before publishing. Nothing becomes community-only or public without an administrator of the owning community setting it.
  5. Add form templates and protocol references that match your own monitoring programs.

Demo data reset: delete rows where the demo flag is set, in each of the organizations, resources, observations, learning, distribution and testing tables.