IndemniCite™ Business Continuity Register

To institute or maintain business workflow transparency, an events register would serve to provide a commanding answer. The business process Risk Managment Department or Legal Compliance Team is the target beneficiary.

The database enables a server-level user to manage business process in a business, workflow register - Secure Task Management, Microsoft Access Database. Developing the database in Microsoft Access, without any MySql or MSSQL Server foreign keys, keeps the security application sequestered from internet intrusion - significantly placing the records at high data integrity risk. The security is enabled via strong password management as part of a One Time Password (OTP), 2-factor authentication security database/API.

For world's best practices, store the Microsoft Access LAN data on a Bluray, optical server, or optical drive for smaller operations - selecting Optical/BDR (one time write only) as the storage. Never select (deletable) flash memory as the option. The optical storage can then be read and written to the web, on a mirror Microsft LAN server, openly and read only networked to other IndemniCite LANs as an IndemniCite WAN (Wide Area Network) Database, for global cooperation. To program directly to MySql and to omit the optical storage is to risk data integrity from a network vulnerability. A gateway database whose URL is promoted on the internet could serve as the login host for all of the IndemniCite platform.

Employ the exchange of contracts to guarantee that any contracted firm has IndemniCite completely deployed and operating to a globally agreed standard. The information collected would be confirmed as of full legal veracity if a declaration to that effect is taken before and after the creation of the individual document, with the use of Xerqon's Digigraph™ Stress Detector.

See the Xerqon blog article 'Global Companies Gazette'™ as an exentension to the solution. The article is availabe fro review at the following link https://www.centreweave.com/post/global-companies-gazette.

All data should be atomised in to logical sets of information, as prescribed by the individual records and their data type in Microsoft Access. Those records will be short text or long text. Short text is best used for summary description. Long text should provide detail of what is described in short text. The relation between the two sets of tables or databases can be queried where the long text record tables are outer-joins of the short text summary table or database, respectively. That is an outer-join or right join.

See the product architectural description below:

SENDER DATABASE

Task Description (VARCHAR)

//Sender describes tasks and auto-signs document with their digital signature (strong password)//

Contacts (VARCHAR)

//Sender assigns contacts//

Schedule (DATE)

//Sender schedules task//

Print Request Report (BOOLEAN)

//Sender saves task and submits//

RECIPIENT DATABASE

Read Report (BOOLEAN)

//Recipients read contact-assigned tasks//

Fulfilment (VARCHAR)

//Recipients fulfil assigned tasks and describe their contribution as large text field//

CHECKLIST DATABASE

Item 1 (BOOLEAN)

Item 2 (BOOLEAN)

Item 3 (BOOLEAN)

. . .

Item N (BOOLEAN)

//Recipients complete task checklist//

FULFILMENT DATABASE

Print Fulfilment Report (VARCHAR)

//Recipients close completed task with their digital signature (strong password) in a short text field//

© Xerqon Pty Ltd 2026