Trust
Manuscript trust begins with clear boundaries.
IgiraPress treats manuscripts as sensitive intellectual property and makes human authority, source honesty, AI limits, and private workflow boundaries explicit.
Manuscript sensitivity
Manuscripts, reports, submission records, author records, editor records, reviewer details, and organization workflow data are sensitive intellectual property and should never be rendered publicly unless a public release process explicitly approves them.
Human judgment
IgiraPress supports editorial preparation and workflow clarity. It does not replace editors, reviewers, publishers, institutions, counsel, or final human decision-makers.
Scholarly authorship
IgiraPress should help authors and editorial teams reason about manuscripts, not silently become the author, reviewer, or publisher of record. Drafting, revision, citation, and readiness support should preserve the author's voice, intellectual responsibility, and disclosure obligations.
Source and citation integrity
Source-backed claims should remain traceable to real, reviewable evidence. IgiraPress should not present fabricated sources, guessed citations, unsupported publication claims, or unverified reference details as scholarly fact.
AI boundaries
IgiraPress may use AI-assisted tools to support manuscript readiness, workflow organization, metadata preparation, and editorial review support. These tools provide signals, not final authority. Editorial, publication, peer-review, institutional, and legal decisions remain human-governed.
Disclosure and work history
Where AI-assisted checks or recommendations affect manuscript preparation, the product should make that assistance visible enough for authors, editors, and institutions to understand what happened, what was suggested, and what still requires human review.
Data protection
Public pages must not fetch private manuscript workflow data. Authenticated routes should fail safely when a token, session, API base URL, or permission is missing, and errors should avoid secrets, stack traces, route internals, tokens, or private metadata.
Product truth
Feature exists, is deployed, and can be smoke-tested.
Feature exists only under authentication, token access, partner access, or configuration.
Feature is roadmap or vision and must be described as future-facing.
Security posture
IgiraPress should operate with access control, least privilege, audit logging where operationally appropriate, clean public errors, production CORS allowlists, and responsible incident response for privacy, security, or unsafe-output events.
Institutional inquiries
Security, privacy, accessibility, and institutional partnership inquiries should have a named escalation path before sensitive manuscript or organization data is exchanged. Until a dedicated address is published, route these inquiries through the official IgiraPress contact channel.