A unified public layer for Sangguniang Bayan information, member workflows, and legislative documents

1. Platform overview

Role in municipal legislative digital service delivery

LIS operates as the public legislative portal for Municipality of Jones, connecting council information, SB member document workflows, session visibility, and DMS-backed legislative reports. The system is implemented as a Laravel application with public web routes and API proxy routes for CMS content.

Unlike a standalone document viewer, LIS maintains member authentication, document forwarding to the SB Secretary (via CMS), session agenda access, and public report pages fed from the Document Management System.

Core platform functions

• Public portal for members, standing committees, district assignments, organization chart, calendar, and barangay officials.
• SB member portal for document upload, forward, edit, and session agenda viewing.
• Legislative document reports: committee reports, resolutions, ordinances, session meetings, executive orders.
• CMS content proxy and secondary database connection for session and meeting data.
• Live stream page for session broadcasts when configured in CMS.

2. System participants

Distinct roles in legislative information and document processing

Public visitors

Browse council information, legislative documents, photo journals, and calendar events without authentication.

Sangguniang Bayan members

Log in via the member guard to upload documents, forward items to the SB Secretary, and view session agendas and remarks.

CMS staff and SB Secretary

Manage content, approve forwarded documents, build session agendas, and publish minutes through the LIS CMS back-office.

DMS administrators

Maintain the legislative document repository consumed by LIS report pages via API and storage URLs.

3. Legislative workflow lifecycle

From member document submission to public visibility

4. Integration routing

CMS proxy, database connection, and DMS document feeds

LIS integrates with CMS through CmsProxyController for storage and API routes, and a cms_mysql database connection for session meetings and related records. DMS integration uses configured API and storage URLs to fetch documents for report pages.

CMS content flow

DMS document flow

5. Public reporting framework

Legislative document categories exposed on the portal

Additional public modules

• Executive orders report page.
• Photo journals and galleries proxied from CMS.
• Live stream integration when CMS live session is enabled.

6. External integrations

CMS API, DMS API, and storage connectivity

• APP_API_URL / CMS_API_URL — CMS endpoints for members, committees, photo journals, and organization data.
• DMS_API_URL / DMS_STORAGE_URL — document listing and file serving for report pages.
• storage/{path} — LIS proxy route to CMS storage for consistent asset delivery.

Related documentation: CMS White Paper · DMS White Paper

7. System architecture

Application and data structure

Presentation layer

Blade views for public portal (/, members, reports) and SB member portal (/sb-members/*), plus this white paper page.

Application layer

Controllers, CMS proxy, member authentication, session controllers, and API routes for CMS data feeds.

Data layer

LIS-local tables for member documents and remarks; CMS database connection for sessions; DMS API for published documents.

8. Security and access controls

Governance, permissions, and integration integrity

• Dual authentication guards: web for standard users and member for SB member accounts.
• Member routes protected by auth:member middleware on dashboard, documents, and sessions.
• Server-side CMS proxy avoids browser SSL certificate issues when fetching CMS assets.
• CSRF protection on member forms; public report pages are read-only.
• DMS document access levels enforced at repository; LIS consumes public listings per deployment policy.

9. Risk management framework

Operational, security, and integration risk controls

Operational risk

Mitigated through document status tracking (draft, forwarded, approved) and secretary approval queues in CMS.

Access risk

Separate member and staff authentication; member documents scoped to authenticated SB accounts.

Integration risk

CMS proxy failures logged; graceful degradation when CMS or DMS endpoints are unavailable.

Data integrity risk

Session document ordering synchronized between member documents and session agenda records in CMS.

10. Operational resilience

Continuity during disruptions

Service continuity depends on CMS availability for council content and sessions, and DMS availability for legislative report pages. LIS supports operational recovery through application logs, manual content updates in CMS when integrations fail, and cached public pages where applicable.

Incident response should follow: detect (logs/alerts), classify severity, contain (disable affected module or proxy), restore CMS/DMS connectivity, verify public report accuracy, and document root cause for governance review.

11. Platform role summary

Legislative portal positioning in one view

LIS, in summary

• Unifies public access to Sangguniang Bayan information and legislative documents for Municipality of Jones.
• Provides SB members a secure channel to submit and forward documents to the secretary.
• Integrates CMS-managed content and DMS-stored records without replacing LGU approval authority.
• Supports live session visibility and comprehensive legislative report categories.
• Designed for white-label deployment across municipal clients (Jones, Buguey, and others).