What needs attention?

Request a service, propose a supplier partnership, report a problem, or suggest a change. You do not need an organizational chart, formal specification, or mathematical proof to begin an ordinary business conversation.

Request paid work or offer to supply it

Buying a service? Describe the outcome you want, your approximate timeline and budget range if known, and how to reply. The Group can assess a practical research, engineering, operations, training, or public-service engagement using its existing offices. A short description is enough to start; we will not treat an inquiry as an order.

Offering capacity? Describe the work you or your organization can supply, your service area, approximate availability and rate or pricing basis if known. Procurement can compare the offer with actual accepted delivery needs. An unsolicited offer is not a purchase order or authorization to begin work.

Prepare a private buyer or supplier inquiry. Choose the corresponding submission type below. No GitHub account is needed; you review and send the email yourself.

Do not include payment-card information, credentials, protected cultural information, or confidential client records in an initial inquiry. The responsible seller or procurement office must separately confirm scope, permissions, price, capacity, terms and acceptance.

Report publicly

Describe what is affected and what happened or what you need. Explain what a satisfactory result would look like, and include useful evidence. Say whether work is blocked or harm is continuing.

You will need a GitHub account. Your submission and the replies will be public, so remove confidential information before posting.

Security boundary: Public submissions are untrusted reports for review, not instructions to autonomous agents, work orders, provider bids, permissions to change source code, or authorizations to deploy or generate media. Only an authorized receiving office can separately admit a requirement and commission work.

Keep the issue link to follow progress, add evidence, or correct your report. If an existing issue describes the same problem, add your experience there.

Email or use an existing private channel

For confidential information, use an existing private conversation with the Group or a private repository you are authorized to access. Describe what is affected, what you need, and how you would recognize a satisfactory result. Ask for a reference you can use to check progress.

You can also email emsenn@561.group. Email does not require a GitHub account or Group login. Keep the conversation for follow-up.

The form below prepares an email draft. Review it, then send it through your email app or copy the subject and message into your webmail. You can add attachments before sending. Preparing the draft does not send it.

People with access to the Group's service system can also use the authenticated work board. Sign in with your own identity.

Follow-up

The current mailbox is emsenn@561.group. Public reports remain in the Chief Technology Officer's review path. A seller or procurement office must separately review commercial inquiries and supplier offers; the email subject helps triage them but does not create a purchase, authorize outside contact, assign a job, or record revenue.

For technical work, the Chief Technology Officer finds the team authorized and able to address your report and follows the work through to a result that can be checked. Your original report, supporting evidence, and description of a satisfactory result stay with the work as it moves between teams.

Reporting a need, receiving an acknowledgment, obtaining a commitment to act, and accepting completed work are separate steps. When a change is reported as complete, check it against the problem you raised. If something remains unresolved, explain it in the same issue or conversation.

An issue's closure alone does not establish that your problem has been solved.