Brigad
FranceStaffing schema v1
Mapped
18%
Components
7
Public map
How Brigad is built
Layer health
What is known, per layer
- People0/4
- Process4/18
- Software2/10
- Data1/7
- Decisions0/1
Lenses
Business architecture: 4 parts. System architecture: 3 parts.
Interfaces and channels
- Native worker appNative worker appA published worker app is retained in the catalog; listing metadata establishes the channel, not a completed login or the rest of the workflow.
- Evidence
- documented
- Public audience routingPublic audience routingThe retained homepage separately addresses professionals seeking missions and businesses seeking qualified staff. These entry paths do not prove an automated lead-to-operations handoff.
- Evidence
- documented
Demand and commitment
- Agreements and documentsAgreements and documentsThe app describes managing contracts, invoices and worker payments; these invoices do not establish a separate client billing interface.
- Evidence
- documented
- Matching and selectionMatching and selectionWorkers receive relevant mission proposals and accept those they want.
- Evidence
- documented
- Offer and acceptanceOffer and acceptanceWorkers receive relevant mission proposals and accept those they want.
- Evidence
- documented
Money and obligations
- Client billing and invoicesClient billing and invoicesApp publisher: business invoicing. Full workflow or decision authority is not established by this description.
- Evidence
- partial
- Worker earnings and payoutWorker earnings and payoutThe app describes managing contracts, invoices and worker payments; these invoices do not establish a separate client billing interface.
- Evidence
- documented
Is this your company?
Claim the profile, correct it, decide what shows
Everything here is public research, labelled as inferred. Create an account to add your own detail in private and choose, value by value, what the registry shows.