Open questions

gap

This register records the brief's known gaps and contradictions found in the source review on 10 September 2026. Each linked page carries the evidence and current interpretation. Resolver roles below are suggested routing, not an established owners table.

The implementation brief owns structure. Source code wins when it contradicts a factual claim. A code-backed claim is verified; prose-only or conflicting knowledge needs verification; missing capability or knowledge is a gap. Public examples and player.lt.org were checked in the browser, and local lt-core was inspected. Other environment URLs remain source-based destinations, not availability checks.

1. gap: Access owners. Who grants each required account and vault? No owners table exists. Expected resolver: Team lead.

2. needs verification: Staging website hostname. DNS uses stg.lt.org targeting lt-stg.pages.dev; Hugo still names staging.lt-web.pages.dev. Confirm the canonical destination. Expected resolver: Web and infrastructure teams.

3. needs verification: Staging CMS hostname. Infrastructure uses cms.stg.lt.org; older automation uses cms-stg.lt.org. Reconcile the configuration. Expected resolver: CMS and infrastructure teams.

4. gap: MPE access and ownership. Supply the engine repository, owner, service URLs and permission model; verify the advertised media-processing features. Expected resolver: Team lead and media team.

5. gap: Public help deployment. Supply the public URL and maintenance owners; resolve placeholder cards and broken hero links. Expected resolver: Help maintainers.

6. Resolved during review: Player documentation hosting. The user supplied player.lt.org; the live v3 showcase links to player.lt.org/docs/. Both were observed on 10 September 2026. The exact deployed revision remains unverified. Expected resolver for revision: player maintainer.

7. needs verification: Public-help product names. The brief maps Expert Video to Publication Plus, but help describes a three-chapter profile introduction resembling Profile Video. Confirm both product-name mappings. Expected resolver: Latest Thinking product owner.

8. gap: Video DOI registration. Choose a registration provider and implement publish-time video DOI minting; the existing reference model has no runtime writer. Expected resolver: Product owner and backend team.

9. needs verification: Coordinator business definition. The stack glossary still marks the institutional persona as candidate knowledge. Expected resolver: Latest Thinking product owner.

10. gap: Stack registry omissions. The manifest omits lt-player, lt-docs and lt-docs-internal. Decide how newcomers obtain them. Expected resolver: Stack maintainer.

11. gap: Monitoring coverage. The brief records no monitoring beyond health checks and backup heartbeats; confirm actual coverage and alert ownership. Expected resolver: Infrastructure team.

12. gap: Push notifications. The brief records notification implementation as missing despite UI copy. Confirm the delivery plan. Expected resolver: Mobile team.

13. needs verification: Production publication trigger. Contrary to the brief, Filament Run mock Publish calls the service. Its visibility lacks an environment restriction; confirm authorized use and production automation. API publication routes remain placeholders. Expected resolver: Backend and product teams.

14. gap: CMS handoff and rebuild trigger. Core payload routes and Hugo content reads exist, but automatic Strapi consumption and the ensuing rebuild are not verified end to end. Expected resolver: Backend, CMS and web teams.

15. needs verification: Source DOI versus video DOI. The brief says the website payload passes through a work DOI; current projection uses the primary source paper DOI. Establish distinct citation semantics. Expected resolver: Backend and product teams.

16. gap: Public links and embed backreferences. The brief describes populated app share fields, but core returns null public URL and DOI and removed embed_snippet. Define completed website backreferences. Expected resolver: Backend and mobile teams.

17. gap: Publication Plus projection. The website payload projector supports Publication and Profile Video, not Publication Plus. Define its editorial integration. Expected resolver: Backend and CMS teams.

18. needs verification: ORCID proof scope. The brief describes universal proof for publication; code gates the creator of researcher-created work, not coordinator-created work. Confirm the intended subject identity requirement. Expected resolver: Product owner and backend team.

19. needs verification: Lifecycle drift. Older curated specs and skills say no runtime machine exists and list extra minor states. Current code has a narrower machine; update upstream guidance. Expected resolver: Backend and stack maintainers.

20. needs verification: Website player configuration. The brief implies an anonymous browser call to the core Video API; core protects it and the website embeds configuration in the page. Confirm the intended future handoff. Expected resolver: Web and backend teams.

21. needs verification: CMS permissions. Schemas and plugins do not establish deployed Editor, Super Admin or anonymous grants. Confirm the role matrix, CSV access and reindex permissions. Expected resolver: CMS administrator.

22. gap: Researcher connection screen. The brief lists connection management as an app capability, but My Connections is hidden as a placeholder. Confirm which actions have usable screens. Expected resolver: Mobile team.

23. needs verification: Mobile distribution. Confirm the current TestFlight invitation process, Android distribution, production publisher decision and absence of over-the-air updates. Expected resolver: Mobile team and team lead.

24. needs verification: Mobile documentation drift. README display names differ from app.config.js; TestFlight build-image prose differs from eas.json. Use code values and update the runbook. Expected resolver: Mobile team.

25. needs verification: Production guide and aliases. Older guides describe pre-cutover targets; DNS and cutover evidence use core.lt.org and cms.lt.org. Alias retirement remains pending in the report. Expected resolver: Infrastructure team.

26. needs verification: Older review and payment guidance. Help describes editorial checks and fees, while core currently disables human editorial review. Confirm what applies to each product today. Expected resolver: Latest Thinking product owner and help maintainers.

27. needs verification: Player license review. The repository license records external legal review as required before stable version 3.0.0. Expected resolver: Player maintainer and client legal owner.

28. needs verification: Public researcher profile sync. Confirm which stored profile fields reach the public page and how editorial updates are reconciled. Expected resolver: Backend, CMS and web teams.

29. gap: Repository onboarding files. Some repositories have no skills directory, and lt-docs has no AGENTS.md or README. Confirm maintainers and first-day entry points. Expected resolver: Repository maintainers.

30. needs verification: Organization and tagline provenance. The brief provides client/vendor names and Making Research Visible; the listed business sources do not independently establish all three. Expected resolver: Team lead and Latest Thinking product owner.

31. needs verification: Legacy retirement. Migration prose establishes intent, not that Drupal, Swift and Vimeo are fully retired. Confirm remaining legacy dependencies. Expected resolver: Product owner and infrastructure team.

32. needs verification: Environment availability. URLs are documented configuration, not a fresh availability check or evidence that access has been granted. Expected resolver: Environment owners.

33. Partly resolved: Internal site hosting. Cloudflare Pages hosts induction.lt.org, verified during deployment review. The intended access policy remains to be confirmed. Expected resolver: Team lead and infrastructure team.

34. gap: Public Publication example. No current Publication URL was found in public navigation or the sitemap. Supply a verified example; the portrait showcase is labelled as a demonstration. Expected resolver: content and web teams.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

• implementation brief

Audience clarification

The review clarified that readers are non-developers without repository access. Developer setup, AGENTS.md reading and source-code access are not induction requirements. Repository omissions remain a maintainer concern, not a task for a new colleague.

35. Product clarification: Acting context. The user clarified during review that only administrators can change acting context and that this is a minor support feature. Earlier source-derived wording described broader account context switching. This guide follows the product clarification; the technical team should reconcile the implementation and source descriptions. Expected resolver: product owner and backend/mobile teams.

36. needs verification: Whimsical status reconciliation. Read the live board via the Whimsical connector on 10 September 2026, including both flow versions and all five tables. It defines 17 statuses versus 13 in code, broader cancellation (including published-state arrows), admin deletion of published work, coordinator final approval, manual LT review and planned notifications. Current code differs, and the two board versions also differ. Confirm the intended version and reconcile the transitions, permissions and notification coverage. Expected resolver: product owner and mobile/backend teams.

37. gap: Canceled-work countdown. Whimsical specifies automatic deletion after 30 days; mobile presentation includes static Deleting in 30 days copy while its comment defers real deadline data. Confirm retention, automatic cleanup and accurate countdown behavior. Expected resolver: product owner and mobile/backend teams.