true-public-access / seagull

Seagull is a toolset to uncage information. To put an eye in the sky that guides us through the maze of bureaucracy and over the mountains of paperwork. To give us the wings to fly and eyes to see the truth.

Seagull

I have found a problem with the current toolset for accessing and understanding public information. Such as PACER EDGAR when it comes to readability and useability for the general public. in the way they have been made by and for lawyers and have technical language due to the need for precision.

Technical goals

• searching through Public information

• Distilling public information into usable resources Describing and graphing relations between public entities And within public entities

• Grounding claims in publicly accessible information

Why this matters

This matters because we have the duty and responsibility to challenge the current systems of repression. we need to know our situation ender to change it. this is the way we take action.

Contribution guide

Contributors are welcomed and needed.

Check out architecture in dev docs to understand the structure of the end goal https://github.com/true-public-access/Seagull/tree/main/devdocs

seagull's Issues

make build compileler

look in to data.gov

Settings Refinement

Request:

This feature is related to settingsedit.py and I suggest refining the file for better handling reading and writing.

Solution:

I suggest the settings.json file be read once during initialization and the contents are stored in a global settings variable. Updates to the settings can be applied to the global variable. The benefit of this is not reading the file every time a setting value is needed. Writes to settings.json can be done every time the setting is updated.

Alternatives:

I do not have an alternative idea. I am, however, open to discussion on the topic.

Add pulled type determination

add why from journal to readme

Add pulled type determination

make list of training sorces

we need a list of training resorses to train or ai powered tools and our grounding database

Create adaptive settings page

Add a settings page that grows with the settings Json

Add Begal architecture to files

think up better name

Refine startup

Fugue out what ai types are needed

Add icon image

add distibuted web hosting and distributed compute functionalitys

make begal repo

Add testing