| title | AMIK Project Context |
|---|
- Last updated:
2026-04-07
- Source:
Workload Metrics - Main.csv - Project type: Laravel maintenance project
- Local repo path:
/Users/aarongilani/Dev_Arena/Laravel/amik-job-board - Product: AMIK Job Board
- Current branch:
fix/open-date-bug - Remote:
git@github.com:ImprobableGenius/amik-job-board.git - Priority: Low at portfolio level
- Load: Low
- Working estimate: 24h total remaining
- Task code prefix:
AMIK - Start date: TBD
- Deadline: Capacity Available
- Status: Maintenance Queue
- Laravel 10
- PHP 8.1+
- Jetstream
- Livewire
- Nova
- Scout with Meilisearch
- Cashier and Spark Stripe
- PostgreSQL
- Vite + Tailwind
- Sentry
- DigitalOcean deployment pipeline
- Project board:
/Users/aarongilani/Dev_Arena/Laravel/amik-job-board/docs/PROJECT_BOARD.md - Project board last updated: March 17, 2025
- Important mismatch: the board says no items are in progress, but the repo currently has an active maintenance branch and a dirty worktree, so the board is stale relative to the codebase
- Board item:
ENH-001 Job Posting Scheduling - Board priority: High within the AMIK project
- Portfolio priority: Low until capacity is available
- Board effort: Medium (
3-5 days) - Working PM estimate:
24h remaining - Active task ID:
AMIK-01
- Employers should be able to create job postings now and schedule them to go live later
- Jobs with a future
open_dateshould stay hidden from the public board until that date arrives - Employer-facing views should distinguish live, scheduled, and past jobs
- Search and indexing should not expose scheduled jobs before they open
JobController::storecurrently publishes jobs immediately withstatus = trueopen_dateexists, but the project board says it currently behaves as display data rather than visibility control- The scheduler in
app/Console/Kernel.phponly unpublishes jobs whenclose_datepasses - Public job visibility currently depends on
statusandclose_date - Search/indexing logic touches:
app/Models/Job.phpapp/Services/JobSearchService.php- Livewire job listing components
- middleware and employer views
- Dirty worktree on
fix/open-date-bug - Modified files:
Dockerfileapp/Models/Job.phpapp/Models/Org.phpconfig/scout.phpresources/views/job/inactive.blade.phpresources/views/jobs.blade.php
- New file:
app/Services/JobSearchService.php
- This strongly suggests ENH-001 has already been partially started in code, even though the project board still lists it in backlog
- This is not a simple 4h maintenance tweak
- The documented enhancement crosses:
- job creation flow
- scheduled publishing logic
- scheduler behavior
- employer dashboard states
- search visibility
- Scout/Meilisearch indexing
- possible credit deduction rules
- tests
- The most likely unresolved product decision is credit timing: whether credits are consumed when a job is scheduled or when it goes live
- Keep this project in the queue until capacity is available
- Do not assign a hard delivery date yet
- Follow-up reminder: if no response is received by Monday, 2026-03-30, send an AMIK check-in and confirm whether
ENH-001should remain parked until capacity opens - When capacity opens, first step should be to review
fix/open-date-bugagainstdocs/PROJECT_BOARD.mdand decide whether to continue that branch or reconcile it withmain
- Board and backlog:
docs/PROJECT_BOARD.md - Job creation flow:
app/Http/Controllers/JobController.php - Scheduler:
app/Console/Kernel.php - Search/indexing:
app/Models/Job.php,app/Services/JobSearchService.php - Public listings:
app/Livewire/JobsIndex.php - Employer views:
resources/views/job/*.blade.php
- AMIK is in maintenance mode, not active sprint delivery
- The queue trigger is available capacity, not calendar urgency
- Current PM reminder is to follow up during the week of
2026-03-30if the client or stakeholder still has not responded - When this project is pulled into active work, treat the first hour as review/reconciliation time because the board and branch state are not aligned