Skip to content

Decide the 2026-27 follow-up capstone direction #29

Description

@yagaC64

Outcome

Make an explicit owner decision on whether to submit a follow-up capstone, for which semester, and which product direction the team can support with real data, users, and acceptance authority.

Status

[DECISION BLOCKED: CAPSTONE OWNER, SEMESTER, AND ACCEPTED PRODUCT DIRECTION]

This is a planning and ownership gate. It does not authorize implementation, procurement, field deployment, a commercial launch, or a production-readiness claim.

Decisions required

  • Confirm whether a follow-up proposal will be submitted.
  • Choose fall, spring, or no submission.
  • Choose one primary direction:
    • field connectivity and API-driven data operations;
    • client-tested launch UX and access model;
    • a deliberately bounded combination with separate deliverables.
  • Name the product owner, faculty/instructor acceptance authority, technical mentor, and student team.
  • Confirm access to any real installation, sensors, communications environment, users, and non-sensitive test data required by the selected direction.
  • Define semester-sized acceptance criteria and a fallback using simulation or synthetic data.

Exit criteria

  • Submission decision and target semester recorded
  • Primary direction selected
  • Owners and acceptance authority named
  • Data, installation, communications, and user-access assumptions verified
  • Semester-sized scope and fallback accepted
  • Child scoping issue selected or both explicitly bounded

Issue/PR Relationship Tree

The children are sibling product options. Neither depends on the other. Selecting one unblocks a focused capstone definition; selecting both requires separate deliverables and explicit semester-capacity evidence.

Boundary

The current repository documents a decision-support MVP. Hardware procurement/build, 24/7 production operations, and unsupported product-commercialization claims remain out of scope unless separately approved and resourced.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions